Packages don't seem to update for around a week right now

[Ronald Klop]

On Sat, 11 Aug 2018 00:43:08 +0200, Maxim Filimonov <che at bein.link> wrote:

> Kevin,
>
> Looks like you're absolutely right.
>
> Moreover, my packages got updates just now. Thank you all for your time  
> and patience.
>


You can see the status of pkg building here:
https://pkg-status.freebsd.org/builds?type=package

current and past builds per platform/version are displayed here:
http://beefy9.nyi.freebsd.org/jail.html?mastername=111amd64-default
http://beefy9.nyi.freebsd.org/build.html?mastername=111amd64-default&build=476857

Regards,

Ronald.


>
> wbr, Maxim Filimonov
> che at bein.link
>
>
>
>> On 11 Aug 2018, at 01:19, Kevin Oberman <rkoberman at gmail.com> wrote:
>>
>> On Fri, Aug 10, 2018 at 1:37 PM Nathan Owens via freebsd-ports <
>> freebsd-ports at freebsd.org <mailto:freebsd-ports at freebsd.org>> wrote:
>>
>>> I haven’t got any lately. I think I heard on BSDNow that builds are  
>>> done
>>> on certain days for different ARCHs
>>>
>>>
>>> Sent from Yahoo Mail for iPhone
>>>
>>>
>>> On Friday, August 10, 2018, 2:16 PM, Maxim V Filimonov <che at bein.link>
>>> wrote:
>>>
>>> Hello everyone,
>>>
>>> I have a bunch of 11.2 machines set up to have the latest packages. The
>>> problem is, the latest pkg branch hasn't been updated since Aug 1.  
>>> What's
>>> the matter with that? Is it just me, or something happened/is  
>>> happening?
>>>
>>>
>>>
>>> wbr, Maxim V Filimonov
>>> che at bein.link
>>>
>>
>> First, I don't believe that they are doing scheduled update any longer,
>> just starting a new one when the old one is completed. This means that  
>> the
>> time between updates is highly variable.Ones with BIG builds like  
>> chromium,
>> libreoffice, etc. can really slow things down. Still, this is a LONG  
>> time.
>>
>> I have seen no update since the new xorgserver port resulted in the  
>> removal
>> of many, many small X ports that are now consolidated into xorgserver.  
>> This
>> also meant the rebuild a a LARGE number of ports that depend on the  
>> removed
>> ports. I had to build over a hundred ports after this on the system  
>> where I
>> build all ports as opposed to using packages. I'm suspicious that this  
>> lead
>> to some problem with the package building system that is preventing the
>> completion of an update.
>> --
>> Kevin Oberman, Part time kid herder and retired Network Engineer
>> E-mail: rkoberman at gmail.com <mailto:rkoberman at gmail.com>
>> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
>> _______________________________________________
>> freebsd-ports at freebsd.org <mailto:freebsd-ports at freebsd.org> mailing  
>> list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-ports  
>> <https://lists.freebsd.org/mailman/listinfo/freebsd-ports>
>> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org  
>> <mailto:freebsd-ports-unsubscribe at freebsd.org>"
>
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"