Re: Stale pkg repo?

2020-12-12 Thread Kevin Oberman
On Fri, Dec 11, 2020 at 10:56 PM Greg Rivers 
wrote:

> On Saturday, 12 December 2020 00:10:04 CST Kevin Oberman wrote:
> > A pkg build in 121amd64 latest was completed on 7-Dec after running for
> > over 90 hours and another on 10-Dec that took a more typical 48 hours
> > build. FWIW, gtk3 is hardly a big package. Try chromium, rust, llvm* or
> > libreoffice. I've seen cases when multiple of these monsters are included
> > in a single build of packages for amd64. My last chromium build took over
> > 13 hours on my build system.
> >
> I have observed similar times. From the spot checks I've done, a full
> build of all packages averages between 50 and 60 hours.
>
> > The pointis that 12.1 latest for amd64 has completed two big builds with
> > the distribution system net getting the updated packages.
> >
> Which brings us back to my original point (for 12.1amd64/latest
> specifically). Why have the repos still not caught up with the builds? If
> rsync is proving unreliable, perhaps switching to replicating via
> incremental ZFS send/receive would be better? Can anyone in the know give
> an ETA on fixing the immediate problem?
>
> --
> Greg
>

The build of 121amd64 latest run started on 2-Dec ran for over 90 hours.
That is the longest I've seen, but there may be longer cases.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Stale pkg repo?

2020-12-11 Thread Greg Rivers via freebsd-ports
On Saturday, 12 December 2020 00:10:04 CST Kevin Oberman wrote:
> A pkg build in 121amd64 latest was completed on 7-Dec after running for
> over 90 hours and another on 10-Dec that took a more typical 48 hours
> build. FWIW, gtk3 is hardly a big package. Try chromium, rust, llvm* or
> libreoffice. I've seen cases when multiple of these monsters are included
> in a single build of packages for amd64. My last chromium build took over
> 13 hours on my build system.
> 
I have observed similar times. From the spot checks I've done, a full build of 
all packages averages between 50 and 60 hours.

> The pointis that 12.1 latest for amd64 has completed two big builds with
> the distribution system net getting the updated packages.
>
Which brings us back to my original point (for 12.1amd64/latest specifically). 
Why have the repos still not caught up with the builds? If rsync is proving 
unreliable, perhaps switching to replicating via incremental ZFS send/receive 
would be better? Can anyone in the know give an ETA on fixing the immediate 
problem?

-- 
Greg


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Stale pkg repo?

2020-12-11 Thread Kevin Oberman
On Fri, Dec 11, 2020 at 4:58 PM Jan Beich  wrote:

> Tatsuki Makino  writes:
>
> > It seems that just 1 package update ( gtk3? :) ) can cause the
> > official poudriere to build a daunting amount of work.
>
> Pales in comparison to FreeBSD security advisiories which force rebuild
> of all 33000 packages. Given package builds are not reproducibile yet[1]
> rsync maybe wasting bandwidth on large packages.
>

A pkg build in 121amd64 latest was completed on 7-Dec after running for
over 90 hours and another on 10-Dec that took a more typical 48 hours
build. FWIW, gtk3 is hardly a big package. Try chromium, rust, llvm* or
libreoffice. I've seen cases when multiple of these monsters are included
in a single build of packages for amd64. My last chromium build took over
13 hours on my build system.

The pointis that 12.1 latest for amd64 has completed two big builds with
the distribution system net getting the updated packages.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Stale pkg repo?

2020-12-11 Thread Jan Beich
Tatsuki Makino  writes:

> It seems that just 1 package update ( gtk3? :) ) can cause the
> official poudriere to build a daunting amount of work.

Pales in comparison to FreeBSD security advisiories which force rebuild
of all 33000 packages. Given package builds are not reproducibile yet[1]
rsync maybe wasting bandwidth on large packages.

[1] https://reviews.freebsd.org/D24586
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Stale pkg repo?

2020-12-11 Thread Tatsuki Makino
It seems that just 1 package update ( gtk3? :) ) can cause the official 
poudriere to build a daunting amount of work.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"


Re: Stale pkg repo?

2020-12-10 Thread Kevin Oberman
On Thu, Dec 10, 2020 at 10:21 PM Greg Rivers via freebsd-ports <
freebsd-ports@freebsd.org> wrote:

> It's been a while since the "latest" FreeBSD pkg repo has been updated.
> For example, dns/bind916 was updated to 9.16.9 ~13 days ago, but has yet to
> appear in the repo.
>
> Has the frequency of pkg builds changed, or is there a problem somewhere
> that's preventing the repo from being updated?
>
> --
> Greg
>
You don't say which version or platform you are using. There have been two
complete repo builds of 12.2amd latest since the last repo update. Looks
like rsync to the distribution systems is hung (again). I dropped a note to
one of the people who have taken care of this in the past yesterday evening
and am hoping for a change tonight (UTC-8). Maybe this thread will get some
notice, as well. I'd like to know the proper place to report this as it has
happened several times in the past year. There really should be a watchdog
on this. Should not be hard to do. I wish I know the longest time a package
update might take after the run is finished before it indicates a problem.
the build of latest can take from a few hours to nearly 4 days. I assume
the rsync time varies by quite a bit, too.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"