| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
PR: ports/85281
Submitted by: Vasil Dimov <vd@datamax.bg>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Perl 5.8.7.
Reported by: mezz
|
|
|
|
| |
Approved by: sobomax
|
|
|
|
|
|
|
|
|
| |
directory
name contains upper-case characters as it makes finding a port harder.
PR: ports/79679
Approved by: will, portmgr(krion)
|
|
|
|
|
|
| |
patches to several appropriately named single-file patches.
Requested by: flz
|
|
|
|
|
|
|
|
|
|
| |
of ports which are depending on a port with a changed shared lib version.
Edwin dedicates this script to his son Dirk, born few days ago :)
Congrats (again) !
PR: ports/63915
Submitted by: edwin
|
|
|
|
|
|
|
|
| |
in the ports framework.
PR: ports/62767
Submitted by: Igor Pokrovsky <tiamat@comset.net>
Approved by: maintainer timeout (> 8 months)
|
|
|
|
| |
Clean up after we're done.
|
|
|
|
|
| |
symlinks are not created on the target) and rsync the entire
directory so that extra files are deleted.
|
|
|
|
|
|
|
| |
default) instead of /tmp, since some packages incorrectly search this
build path at runtime to try to load things.
Requested by: nectar
|
| |
|
|
|
|
| |
make it the default behaviour.
|
| |
|
|
|
|
|
|
| |
need them when building from 'addport -a -t'.
Approved by: will
|
| |
|
|
|
|
|
| |
Submitted by: Christopher Kelley <bsd at kelleycows.com>
Pointyhat to: krion
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Fix PATH problems during README.html generation if "make
-DPORTSTOP readmes" is defined. [2]
* Add support for early rcNG startup scripts. [3]
* Remove duplicate USE_XLIB handling. [4]
* Add check for USE_PYTHON_(BUILD|RUN), and include bsd.python.mk if
both are specified. [5]
* Use PRE-INSTALL target for SUB_FILES and SUB_LIST. [6]
* Introduce bsd.gstreamer.mk and utilize new macros:
USE_GSTREAMER/WANT_GSTREAMER. [7]
PR: ports/77634 [1], ports/77592 [2], ports/77385 [3],
ports/77557 [4], ports/77344 [5], ports/77211 [6],
ports/77838 [7]
Submitted by: krion [1] [2], Florent Thoumie <flz@xbsd.org> [3] [6],
pav [4], lofi [5], ahze [7]
|
|
|
|
|
|
|
|
|
| |
look for processes holding open references within the FS and kill
them, then use regular umount. This is necessary now that devfs
cannot be force-unmounted, and has the benefit that processes can't
hang around holding references to files between port builds.
* Preliminary work to support using ccache to accelerate builds.
|
|
|
|
| |
(i.e. it is not mounted by nfs)
|
|
|
|
|
|
|
| |
processes holding open references within the FS and kill them, then use
regular umount. This is necessary now that devfs cannot be force-unmounted,
and has the benefit that processes can't hang around holding references to
files between port builds.
|
|
|
|
|
|
|
|
|
|
|
| |
look for processes holding open references within the FS and kill
them, then use regular umount. This is necessary now that devfs
cannot be force-unmounted, and has the benefit that processes can't
hang around holding references to files between port builds.
* Reduce possibility for error by testing for presence of executable
ldconfig inside the chroot before attempting to run it (e.g. it may not
be there if the chroot was not completely initialized)
|
|
|
|
| |
false positives.
|
| |
|
|
|
|
| |
send nag-mails to the responsible maintainers.
|
|
|
|
|
|
| |
which are copied to www.freebsd.org for use by 'make fetchindex', as well
as the source of build failure reports on ports@FreeBSD.org when it is
broken.
|
| |
|
|
|
|
|
|
| |
This should probably be changed to only update it if it changes.
Approved by: portmgr (self)
|
|
|
|
|
|
| |
want to use the default value in the build chroot.
Approved by: portmgr (self)
|
|
|
|
|
|
|
| |
if the machine is behind a NAT and is not directly addressable, we can
use a localhost port forward to contact it)
Approved by: portmgr (self)
|
|
|
|
|
|
|
|
| |
value of variables
* Allow krion to drink from the email firehose
Approved by: portmgr (self)
|
|
|
|
|
|
|
|
| |
* Correctly calculate job concurrency in pass two as well
* In pass two run dosetupnode -rsync to avoid wasting time.
Approved by: portmgr (self)
|
|
|
|
|
|
| |
XXX This should be a portbuild.conf tunable
Approved by: portmgr (self)
|
|
|
|
|
|
|
|
| |
fetch from ftp-master and pointyhat; they'll just get timeouts.
Instead, each machine is expected to set up their own MASTER_SITE_*
variables in etc/make.conf via a bindist-${hostname}.tar file.
Approved by: portmgr (self)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
on a disconnected client, without running the time-consuming rsyncs.
This is useful when a build is interrupted and needs to be restarted.
* After we have cleaned up the machine, reset the queue counter by using
pollmachine -queue. This has a race condition if other builds are being
dispatched to the machine (e.g. builds on another branch):
getmachine can claim a directory and increment the counter, then the
machine is polled and finds e.g. 0 chroots in use, and resets the
counter to 0, then claim-chroot is run and the build dispatched, with
the counter now off-by-one. This could be fixed by running
claim-chroot with the .lock held, but this turns out to be too
time-consuming. A two-level lock approach might also fix this
efficiently.
|
|
|
|
|
|
|
|
|
|
| |
same time, assuming that the admin has already built the INDEX and
INDEX.old in advance.
* Adapt to new method of calculating build concurrency, by summing the
value of ${maxjobs} listed in every portbuild.${machine}
* Support 5-exp builds
|
|
|
|
|
|
|
|
|
|
|
| |
(i.e. if the package lists a dependency on the relevant package in the
PACKAGE_BUILDING case). This allows packages that require an
available DISPLAY to again build (with some forthcoming fixes to
existing ports).
Improve the reporting of detected filesystem anomalies (extra files
left behind after deinstallation, changes to and removal of
pre-existing files)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
synchronously instead of probabilistically scheduling jobs, which
means that the job load on a machine never exceeds a desired
threshold, and we can preferentially use faster machines when they are
available. This has a dramatic effect on package build throughput,
although I don't yet have precise measurements of the performance
improvements.
Specifically, the changes are:
* Introduce the new variable maxjobs in portbuild. This replaces the
build scheduling weights previously listed in the mlist file, which
now changes format to list the build machines only, ranked in order of
preference for job dispatches (i.e. faster machines first).
* The ${arch}/queue directory is used to list machines available for
jobs (file content is the number of jobs currently running on the
machine). Changes to files in this directory are serialized using
lockf on the .lock file.
* Claim a machine with the getmachine script, with the .lock held.
This picks the machine with the fewestnumber of jobs running, which is
listed highest in the mlist file in case of multiple machines with
equal load. The job counter is incremented, and the file removed if
the counter reaches ${maxjobs} for that machine. If all machines are
busy, sleep for 15 seconds and retry.
* After we have claimed a machine, we run claim-chroot on it to claim
an empty chroot, as before. If the claim fails, release the job from
the queue with the releasemachine script and retry after a 15 second
wait.
* When the build is finished, decrement the job counter with the
releasemachine script, with .lock held.
* The checkmachines script now exists only to poll the load averages
for admin convenience (every 2 minutes), and to ping for unreachable
machines. When a machine cannot be reached, remove the entry in the
queue directory to stop further job dispatches to it. This needs more
work to deal with reinitialization of machines after they become
available again.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
synchronously instead of probabilistically scheduling jobs, which
means that the job load on a machine never exceeds a desired
threshold, and we can preferentially use faster machines when they are
available. This has a dramatic effect on package build throughput,
although I don't yet have precise measurements of the performance
improvements.
Specifically, the changes are:
* Introduce the new variable maxjobs in portbuild. This replaces the
build scheduling weights previously listed in the mlist file, which
now changes format to list the build machines only, ranked in order of
preference for job dispatches (i.e. faster machines first).
* The ${arch}/queue directory is used to list machines available for
jobs (file content is the number of jobs currently running on the
machine). Changes to files in this directory are serialized using
lockf on the .lock file.
* Claim a machine with the getmachine script, with the .lock held.
This picks the machine with the fewestnumber of jobs running, which is
listed highest in the mlist file in case of multiple machines with
equal load. The job counter is incremented, and the file removed if
the counter reaches ${maxjobs} for that machine. If all machines are
busy, sleep for 15 seconds and retry.
* After we have claimed a machine, we run claim-chroot on it to claim
an empty chroot, as before. If the claim fails, release the job from
the queue with the releasemachine script and retry after a 15 second
wait.
* When the build is finished, decrement the job counter with the
releasemachine script, with .lock held.
* The checkmachines script now exists only to poll the load averages
for admin convenience (every 2 minutes), and to ping for unreachable
machines. When a machine cannot be reached, remove the entry in the
queue directory to stop further job dispatches to it. This needs more
work to deal with reinitialization of machines after they become
available again.
Additional changes to this file:
* Exit if passed a null package name, to avoid badness later on
* Send a nag-mail if pkg-plist errors are detected in the build
|
|
|
|
| |
* Other minor changes
|
|
|
|
|
|
|
|
|
| |
/rescue/mount -t linprocfs, so assume that the i386 build hosts have
statically-built copies of the necessary binaries in /sbin, until this is
fixed.
Create /usr/X11R6 inside the chroot so that mtree has something to do, since
this directory is otherwise orphaned.
|
| |
|
| |
|
|
|
|
| |
the BSD.x11.dist if set to xfree86-3, otherwise use BSD.x11-4.dist.
|
|
|
|
| |
on pointyhat.
|
|
|
|
|
| |
Submitted by: linimon
Reminded by: marcus
|