On 3/8/19 5:11 PM, Miro Hrončok wrote:
On 08. 03. 19 18:39, Miro Hrončok wrote:
> On 08. 03. 19 18:26, Kevin Fenzi wrote:
>> On 3/7/19 12:30 PM, Miro Hrončok wrote:
>>> On 07. 03. 19 21:19, Kevin Fenzi wrote:
>>>> On 3/7/19 11:35 AM, Tomasz Kłoczko wrote:
>>>>> On Thu, 7 Mar 2019 at 12:17, Fedora Rawhide Report
>>>>> <rawhide(a)fedoraproject.org> wrote:
>>>>>>
>>>>>> OLD: Fedora-Rawhide-20190217.n.0
>>>>>> NEW: Fedora-Rawhide-20190306.n.1
>>>>>>
>>>>>> ===== SUMMARY =====
>>>>>> Added images: 13
>>>>>> Dropped images: 7
>>>>>> Added packages: 128
>>>>>> Dropped packages: 174
>>>>>> Upgraded packages: 1745
>>>>>> Downgraded packages: 165
>>>>>
>>>>> Looks like it is second or third time when after report about
release
>>>>> some batch of the packages nothing hit the ground/public repos.
>>>>> My understanding is that it is some glitch in release
infrastructure.
>>>>> May we know what is the current situation?
>>>>
>>>> What ground/public repos do you mean here? The master mirror is
>>>> definitely updated. It's a large pile of changes, so other mirrors
may
>>>> take a bit longer than normal to sync.
>>>>
>>>> There's no glitch I am aware of, so more information would be
helpful.
>>>
>>> This seems quite OK:
>>>
>>>
https://admin.fedoraproject.org/mirrormanager/propgation
>>>
>>> Yet all the mirrors I try randomly show Fedora-Rawhide-20190217.n.0
>>
>> Well, perhaps you looked at it too soon?
>>
>> Right now it's slowly showing mirrors catching up over the last 12 hours
>> or so.
>
> Perhaps. I see the progress now, thanks!
I also wonder if no new composes even starting is a deliberate choice or
some kind of error:
https://kojipkgs.fedoraproject.org/compose/rawhide/
The rawhide compose is in a cron job, set to fire at 5:15UTC.
However, if there's already one running it will just exit and not launch
a new one. Yesterday at that time the completed one wasn't finished, so
the cron didn't start a new one. The rawhide compose job at the end
cleans up old composes older than 2 weeks, and last nights was the first
one to finish in a long time, so it had a lot of old composes to clean up.
We should probably move that cleanup to a separate job, but we haven't yet.
kevin