Matthew Trescott wrote:

Per Jessen wrote:

...

Hi Matthew

if Provo still hasn't caught up, maybe try re-building your project, that ought to get it pushed out again.

Thanks Per—

I disabled publishing the repository in OBS this morning (UTC minus 4) but it hasn't yet disappeared from download.O.O or the Provo mirror (is that normal?).

Hmm, I'm not sure how disabling publishing will affect what is actually pushed out.

I just ran osc wipebinaries --all so it is rebuilding but I'm not sure that will change what it is doing either.

It's been a couple of days, has the situation improved ? -- Per Jessen, Zürich (13.1°C) Member, openSUSE Heroes

Matthew Trescott wrote:

Per Jessen wrote:

...

Hmm, I'm not sure how disabling publishing will affect what is actually pushed out.

Yes, I'm not sure either. I thought it deleted the repository on download.O.O but I guess not.

...

...

I just ran osc wipebinaries --all so it is rebuilding but I'm not sure that will change what it is doing either.

It's been a couple of days, has the situation improved ?

It isn't easy to tell whether that made a difference since download.O.O doesn't show any changes after I disabled publishing the repository. Should I try reenabling it?

I would reenable it, yes.

I suspect something else is going on, since Provo hasn't synced my repository in months and I updated packages during that time although I never did a full rebuild.

repository changes are actively pushed to the Provo mirror, but only when something actually changes. -- Per Jessen, Zürich (12.2°C) Member, openSUSE Heroes

Matthew Trescott wrote:

...

repository changes are actively pushed to the Provo mirror, but only when something actually changes.

But... things /were/ actually changing when I was updating my packages. I guess I wasn't clear exactly; the fact that Provo wasn't synching doesn't seem to be related to my disabling builds last October/November. Disabling and reenabling the builds last autumn was what made me realize that Provo had stopped syncing. Other people's home projects show the same behavior. Here's another random example; compare download.O.O vs the Provo mirror:

http://download.opensuse.org/repositories/home:/aschnell/openSUSE_Factory/ http://provo-mirror.opensuse.org/repositories/home:/aschnell/openSUSE_Factor...

It seems to me there must be something wrong with the way home project repositories are synced to Provo.

Those two above both seem empty though, just directories. How about we look at yours specifically ? -- Per Jessen, Zürich (15.3°C) Member, openSUSE Heroes

Matthew Trescott wrote:

Per Jessen wrote:

...

How about we look at yours specifically ?

Sure—the easiest example is this one:

http://download.opensuse.org/repositories/home:/matthewtrescott:/openproject...

No mirror has synced the package. Provo still has OpenProject 11.0 even though I pushed out 11.0.1 on November 6, 11.1.0 on December 20, 11.1.2 on January 22, 11.1.4 on March 3, and most recently, 11.2.4 on May 12. There aren't any file name conflicts in this case because these are not just rebuilds.

I see different versions in different places - ftp.gwdg.de - 11.1.4, dated 11 Apr 2021. provo - 11.0.0, dated 1 Nov 2020. lysator - 11.1.4, 11 May 2021 widehat - 11.1.4, dated 11 Apr 2021. Looking at the logs for April and May, your project was pushed : 5 Apr, lysator 11 Apr, gwdg, lysator, widehat 17 Apr, lysator 11 May, lysator. I have opened an issue, https://progress.opensuse.org/issues/92927 -- Per Jessen, Zürich (13.0°C) Member, openSUSE Heroes

Matthew Trescott wrote:

Per Jessen wrote:

...

I have opened an issue, https://progress.opensuse.org/issues/92927

Thank you for investigating this!

Check out the ticket for an update (it should be publicly available), but all of the push mirrors are now up-to-date. -- Per Jessen, Zürich (12.5°C) Member, openSUSE Heroes