aboutsummaryrefslogtreecommitdiffstats
path: root/Tools
Commit message (Collapse)AuthorAgeFilesLines
* Eliminate more false positives for install_error. Very noticeable onlinimon2006-12-261-1/+1
| | | | latest gcc test build.
* Query Gnats for PRs by using the query-pr command on freefall instead of thevd2006-12-201-2/+22
| | | | web-interface becase the later is not reliable.
* Add check for existing non-closed PRs related to the port being removed.vd2006-12-131-1/+65
| | | | | If any are found then ask if the port should be skipped from removal or removed regardless of the PRs.
* - add check sysvipcdinoex2006-12-041-0/+2
| | | | happens when security.jail.sysvipc_allowed=0
* Work around the fact that 5-exp, these days, is really another 6-exp,linimon2006-11-251-0/+4
| | | | except in disguise.
* Replace a simple call to localtime() to strftime() to include theerwin2006-11-231-1/+2
| | | | timezone.
* eik@ has been inactive for quite some time and as I am runningerwin2006-11-234-3/+6
| | | | | these scripts on the cluster, transfer maintainership of these to myself.
* Include a time when the script was started in the mail templates.erwin2006-11-231-5/+16
| | | | | | | This script can sometimes take several hours to run on builder, and thus leading to confusing of why it still reports an error that was fixed in cvs some time ago. Including the time when the ports tree was updated should reduce some of this confusion.
* Add deprecated reason to the output of -Fvd2006-11-021-2/+6
|
* * Create custom commit message template and populate it with the portsvd2006-11-011-16/+88
| | | | | | | | | | | to be removed, possibly with the expiration date and deprecated reason * If port is not marked for expiration than put "Removed" in ports/MOVED entry instead of "Has expired" * Implement -a option to remove all expired ports * Ask if the cvs diff output should be recreated/reviewed again thus giving the committer a chance to edit files by hand and view diff results afterwards * Cosmetic changes
* When checking for dependencies of foocategory/barport also find constructsvd2006-10-051-1/+1
| | | | | like .../barport/something e.g. expect either space, slash or eol after port's name
* Since we already have the data from the grep, go ahead and make the 'latestlinimon2006-09-231-5/+4
| | | | | log' cell a link to it. My weak awk/sh skills are evident here, but it does the job.
* Add links to cvsdone and INDEX files. Add some whitespace.linimon2006-09-231-2/+17
|
* When checking dependencies also look for portname references in Mk/*.mkvd2006-09-141-5/+5
| | | | in addition to */*/Makefile* and ignore references in comments
* * Back up duds to duds.old before, not after we create the new onekris2006-09-141-59/+81
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add more XXX comments for future work * Only record a cvsdone timestamp if we updated cvs * When building with -trybroken, it's safe (and desirable) to run the prunefailure script * Reorganise a few things for better parallelism * Instead of keeping a duplicate copy of the previous logs and errors under bak/, just store a symlink to the archival location * When doing an incremental build, also cycle out the old logs to avoid broken links on the website (the logs from the previous build are removed until the packages are rebuilt). Use cpio to create hardlinked copies of the previous logs. XXX when these are bzipped by cron to save space the links will be broken and it might actually take more space. * Don't bother bunzipping old logs, now that the processlogs scripts can handle it. This was a waste of time anyway since they'd all be rebzipped by the next nightly cron job. * When the build is complete, stash a copy of the restricted ports in bak/restricted/ before deleting them from packages/, and restore from here when doing an incremental build to avoid needlessly rebuilding them each time.
* * When calculating the IP address to use for the jail, don't usekris2006-09-141-4/+5
| | | | | | | 127.0.0.0 or 127.0.0.1 * Don't use chroot to mount the linprocfs, or it won't be visible within the jail.
* * Support bzipped logfileskris2006-09-141-122/+127
| | | | | * More robust extraction of the header values (copes with the addition of the build uname to the header)
* * If .force exists, rebuild index unconditionallykris2006-09-141-5/+6
| | | | | | | * Support .log.bz2 files * Clarify that BROKEN ports are not frequently rebuilt so probably won't appear
* Correct typo in previous commitkris2006-09-141-2/+2
|
* * Drop alpha supportkris2006-09-141-6/+7
| | | | | | | | | | * Increase sparc64 build timeout to 24 hours (we have so few build machines that we cannot afford to tie them up for longer) * Increase other arch build timeout to 100 hours (hello openoffice!) * If we successfully build a formerly broken package, touch errors/.force which will kick off a rebuild of the html files
* * Retire 4-exp builds and add support for 6-exp.kris2006-09-141-11/+12
| | | | | | | | | * Use a generation number for the bindist tarballs, with compatibility symlink. Eventually we'll use this to avoid building in a "stale" chroot (i.e. populated by old world). * Don't bother running ldconfig on i386, it is evidently not needed since the other arches work fine without it
* * Silence gconf spam from the mtree checks (for now)kris2006-09-141-4/+5
| | | | | | | | * Don't try and mount/umount procfs, it won't work when we build inside a jail. * Report the uname -mr of the build environment, to ease confusion of people reading the error logs by mail.
* * Use SRCBASE for source locationkris2006-09-141-6/+12
| | | | | * The 5.x variant for populating /etc does not work on 6.x and above, and vice versa. Conditionalize old and new methods.
* Go back to force unmounting because not doing so was too unreliable.kris2006-09-141-2/+2
|
* Silence the clean-chroot invocationkris2006-09-141-1/+1
|
* Remove grep's -w switch from the dependency check since it misses somevd2006-09-121-1/+1
| | | | | dependencies. This needs some more polishing but for now it is better to emit false positives than skip dependencies.
* Get rid of multiple false positives for "arch" due to compiler warning;linimon2006-08-211-3/+1
| | | | fix true positive for "runaway_process".
* Catch a few more new cases of linker error; reclassify most of the linkerlinimon2006-08-191-0/+4
| | | | | errors seen on -CURRENT as "compat6x" e.g. "someone needs to create a compat6x port and then make it a dependency here."
* Add support for DESTDIR part I.erwin2006-08-041-10/+40
| | | | | | | | | | | | | | This commit should largele be a NOOP as it only adds support for DESTDIR undefined. This does allow us to start testing ports with DESTDIR set, but this is as of yet not supported. Although this has been extensively tested on pointyhat, this is a very intrusive change and some cases may have been overlooked. Please contact Gabor and me if you find any. PR: 100555 Submitted by: gabor Sponsored by: Google Summer of Code 2006
* Catch another case of 'disk full'.linimon2006-08-011-1/+1
|
* Change locking from per architecture to per architecture and branch.erwin2006-07-301-1/+2
| | | | | Especialy i386 has enough horsepower to run two branches simultaniously. This change has been on pointyhat for some time.
* Add an option to the addport script: -b requests that any files inshaun2006-07-141-3/+22
| | | | | | | | ${FILESDIR} which look like patches be treated as binary files. This prevents RCS tags in patch fragments causing a problem for CVS. Approved by: garga (maintainer), ahze (mentor, implicit)
* Add the cvs checkout date so people can see how long the runs take; addlinimon2006-07-131-3/+20
| | | | a comment about openoffice.org*; generalize a bit.
* Make it a little more robust.linimon2006-07-101-1/+1
|
* Convenience script to tersely display all currently running package builds.linimon2006-07-101-0/+11
|
* 'portcomment' appears to be obsolete.linimon2006-07-091-2/+0
|
* Fix the disk_full rule.linimon2006-07-091-1/+1
|
* Add the -exp builds down at the end. Probably only of interest to portmgr,linimon2006-07-081-11/+32
| | | | | so do them separately in order not to break up the ease of browsing the most important stats, above.
* White space adjustment after refactoring.linimon2006-07-081-21/+21
|
* Refactor. No code change (yet).linimon2006-07-081-11/+31
|
* Add some color to the display.linimon2006-07-061-17/+30
|
* Fix CVS tag.linimon2006-07-061-1/+1
|
* Refactor. No code changes yet.linimon2006-07-061-16/+16
|
* Add a column for last-date stamp and clean up the formatting a bit.linimon2006-07-061-7/+22
|
* Escape characters (like +) that may appear in ports' names andvd2006-07-051-2/+13
| | | | break sed -E regular expressions
* When automatic commit log is generated, change @ to " at " on submitter emailgarga2006-07-051-0/+1
| | | | to prevent spam
* Handle the case where the size of INDEX is zero (e.g. during new builds).linimon2006-06-291-1/+5
|
* Fix edit-o.linimon2006-06-281-1/+1
|
* Creates an HTML file with tables for each architecture which summarize thelinimon2006-06-271-0/+123
| | | | | number of packages built vs. packages that failed, along with some other related information.
* - Remove false positives for 'makefile' (and possibly a few others).linimon2006-06-251-57/+23
| | | | | | | | | | | | | | | | | | | | | | | - Remove obsolete explanations which are no longer seen, for speed: ELF, MOTIF, MOTIFLIB, X_manpage, awk, bison, ffs_conflict, forbidden, getopt, getopt.h, imake, lc_r, malloc.h, pod2man, sed, stl, soundcard.h, texinfo, union_wait, values.h - Add more cases to: arch, bad_c++, compiler_error, depend_object, install_error, linker_error, mtree, perl5 These changes reduce many dozens of false positives; add a few dozen true positives; and for certain directories, improve the speed about 10% (a few drop by 15%). It turns out that the performance issues are mainly due to the multiple greps. If performance is an issue we need to go back to the moderately- unreadable, everything-on-one-line paradigm. Before that happens, I would like to experiment with some refactoring, so that the patterns are built up in the shell line-by-line, so you could still be able to read it. Tested on: pointyhat Hat: portmgr
* MFP4:erwin2006-06-231-1/+1
| | | | | Actually use ${SCP_DEST_TMP} to fix the case where SCP_DEST_TMP != /tmp/
* MFP4:erwin2006-06-191-6/+24
| | | | | | When copying INDEX to the server, copy it first to a staging area and first then to the real location. The copying can take long enough for users to get a truncated file when downloading during the upload.
* - Change addport script to do the job locally instead connect to freefall everygarga2006-05-162-18/+39
| | | | | | | | | | time to add a new module. If you want to still use old way, just use "-M freefall.FreeBSD.org" option - Take addport maintainership - When modulesupdate fail, ask user to retry - Change modulesupdate to work fine with addport Approved by: will (maintainer)
* Add support for specifying ports to be removed as directories on thevd2006-05-021-1/+27
| | | | | | | | filesystem (either absolute or relative) in addition to `category/port'. PR: ports/96649 Submitted by: Cheng-Lung Sung <clsung@freebsd.org> Reworked by: vd
* Improve dependency check:vd2006-05-021-2/+3
| | | | | | When removing category/port - look if other ports' Makefiles contain `/port' rather than `category/port', since the later misses things like `${.CURDIR}/../port'
* Add support for removing multiple ports which depend on each othervd2006-04-171-36/+48
|
* Explicitly mount the NFS images ro, instead of relying on the server tokris2006-04-161-1/+1
| | | | | export it ro. This saves thrashing the server if we accidentally try to rm -rf a NFS mount (e.g. because a chroot cleanup failed).
* Don't bother archiving the ports tree, we don't use it for anything so itkris2006-04-161-1/+1
| | | | just takes up time.
* Quote ${1} so we don't get ``[: =: unexpected operator'' if the scriptvd2006-04-121-1/+1
| | | | is started without arguments.
* Add the script I use to remove ports so everyonevd2006-04-101-0/+315
| | | | can benefit (or suffer :-) from it.
* Mount linprocfs on amd64 for the convenience of jdk builds.kris2006-04-031-1/+1
|
* The squid rc.d script no longer has the .sh suffixkris2006-04-032-4/+4
|
* Do not preserve the previous package sets in bak/. This is taking upkris2006-04-031-2/+2
| | | | too much space on pointyhat, and it's also very slow.
* Clean up linprocfs on amd64 as well.kris2006-04-031-1/+1
|
* jdk is buildable on amd64, so we need to also mount linprocfs there.kris2006-04-031-2/+2
|
* This script preserves packages that will be removed by the restricted.shkris2006-04-031-0/+11
| | | | | | | | script, i.e. so they can be moved back into place before start the next incremental build so they won't be needlessly rebuilt every time (jdk, I'm looking at you). It is a bit of a hack since it relies on assumptions about the structure of that shell script, but for now it's the best we can do.
* Temporarily back out the pre.log change, it doesn't work properly.kris2006-03-131-6/+6
| | | | Approved by: portmgr (implicit)
* Mount the md image async here tookris2006-03-131-1/+1
| | | | Approved by: portmgr (implicit)
* Add some more directories temporarily until these ports can be made tokris2006-03-131-4/+8
| | | | | | clean themselves up properly. Approved by: portmgr (implicit)
* Add a mechanism for reporting client machine error conditions back to thekris2006-02-151-1/+14
| | | | | | | | | | | server. Error conditions are flagged by other processes by creating a named dotfile in ${scratchdir}. If these files are found, report the error status instead of the number of running jobs. Currently report "ERR" for all error conditions; I will probably change this to a per-condition message. Currently only "squid not running" and "disk space low" conditions are reported.
* Trim some unused cruftkris2006-02-151-69/+12
| | | | | | | If the package copy fails, bail out immediately instead of later on when we try to pkg_add it. Also trap signals and bail out. Both conditions will cause a retry of the package build.
* Save the output of portbuild run on the client to a temporary log file.kris2006-02-151-1/+11
| | | | | | | | | | If portbuild bailed out unexpectedly, mail the log to ${mailto}. Add some XXX comments about improving robustness of this script. Sleep for 2 minutes before retrying builds, to avoid spamming ${mailto} with a high rate of failure logs. In future we might be smarter about attempting to automatically correct common failure modes.
* Add some sanity checking of the build environment:kris2006-02-151-1/+30
| | | | | | | | | | | * Test whether squid is running. If not, try to kick off the rc script in the background in case it can be restarted cleanly. * Test for at least 100MB of free space on the scratch partition. If either condition fails, set an exception flag and bail out. This will be reported back to the server via reportload.
* * Don't try to pkg_delete packages that are not installed (the usualkris2006-02-151-6/+9
| | | | | | | | | | cause is because it was specified in the list twice) * Don't panic when the list of packages to delete becomes empty * When unexpected filesystem changes are detected, bail immediately instead of proceeding and hiding the error in the middle of the log
* Add support for 6-exp builds (FreeBSD 6.x is our new reference platform)kris2006-02-154-4/+14
|
* * Switch back to using pkg_delete -f; we are not yet ready to dealkris2006-02-141-25/+26
| | | | | | | | | with all the errors from broken pkg_delete scripts * As threatened in previous commit, move the pristine mtree spec generation to phase 1, and avoid having to delete and re-add the FETCH_DEPENDS. We still have to keep them installed until after 'make extract' though
* * In kill_procs(), pass in the directory and mountpoint as separatekris2006-02-111-2/+8
| | | | | | | | | | | arguments (cosmetic) * Detect if a chroot was used to run a jailed build, and first attempt to gracefully shut it down by killing everything within using pgrep(1) This has a much higher chance of succeeding that relying on fstat to identify processes that might interfere with our attempts to clean up mountpoints, which is fragile (libkvm-dependent), and inherently unreliable at best.
* Support for building ports in a jail instead of a chroot. If use_jail=1kris2006-02-111-9/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in portbuild.conf (or per-machine .conf), then construct a 127.0.0.0/8 IP address based on the build directory ID (i.e. unique for each build instance). This is bound to the lo0 interface for the duration of the 'phase 2' build. We cannot build 'phase 1' in a jail since 'make fetch' doesn't always work through a proxy (e.g. squid sometimes mangles files fetched through FTP, I think by performing CR/LF translation in FTP ASCII mode). Pass in the HTTP_PROXY variable to the jail, if set. This allows FTP/HTTP access from within the jail if the proxy is suitably configured (some ports legitimately need to fetch additional files during the build, e.g. if they have a BUILD_DEPENDS=...:configure target that needs to fetch additional distfiles). Not all ports can be built in jails (most notably the linux_base ports since they want to mount/umount linprocfs), so we will need to come up with a way to deal with this. Some ports require SYSV IPC, so security.jail.sysvipc_allowed=1 might be required. Some other ports attempt to perform DNS lookups, ping, or outbound TCP connections during the build. When it works, this provides better compartmentalization of package builds, e.g. easier termination of builds without the possibility of daemonized processes staying active; no possibility of accidental interference between jails, etc. It also allows for admin monitoring using jls(1).
* * Use ${mailto} portbuild.conf variable instead of hard-coded list [1]kris2006-02-111-4/+7
| | | | | | | | * Remove old logs and possible compressed logs before attempting the build Requested by: lofi [1] Submitted by: linimon [1] No more accidental portbuild spam: kris and krion [1]
* Use ${mailto} portbuild.conf variable instead of hard-coded listkris2006-02-111-1/+1
| | | | | | Requested by: lofi Submitted by: linimon No more accidental portbuild spam: kris and krion
* Checkpoint a major round of changes:kris2006-02-111-64/+201
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Only keep distfiles if the port passes 'make fetch', so we don't accidentally keep files with invalid checksums * Use cleanup() instead of directly exiting in some error conditions * When cleanup() is called indicating an unexpected error (possibly leaving the filesystem in an inconsistent state), mark the chroot as dirty so it will not be reused by another build * Remove packages in dependency order instead of with pkg_delete -f in possibly incorrect order. This paves the way for focusing on errors generated by pkg_delete (e.g. @dirrm that should be @dirrmtry) in the future. [1] * Detect when packages were left behind because they were still in use by other packages, indicating an incorrect or incomplete port dependency list * Partial support for ccache builds (not yet complete) * Support non-standard LOCALBASE/X11BASE settings * Delete FETCH_DEPENDS after the 'make fetch' stage. We have to add them again before 'make extract' since, due to a lack of a 'fetch cookie', 'make extract' actually *always* runs 'make fetch' again, even when distfiles have already been fetched. We need to delete them in order to: * Record an mtree spec of the 'pristine' filesystem state, for later comparison. # XXX Perhaps this can be done in stage 1 before the # 'make fetch', removing the need to delete-and-readd. * Also record an mtree spec of the filesystem state prior to the build phase. Compare this to the state of the filesystem immediately before running the install phase, to detect files that were inappropriately installed during the build phase. Doing so is a fatal error. * Prior to installing, try to run a 'regression-test' port makefile target, if it exists. This allows ports to hook their internal regression suites into the package build. This needs further infrastructure support, e.g. a default NOP target in bsd.port.mk. For now this is run with 'make -k', so regression failures will not yet actually cause package build failures. * Separate the 'make install' from 'make package' phases rather than let the latter implicitly do the install. * After the newly packaged port has been deleted, compare the state of the filesystem to the state before 'make install'. * After removing BUILD and RUN dependencies, compare the filesystem state to the pristine state before the start of the build. This also detects package dependencies that did not clean themselves up properly when deinstalling. It also detects dependencies that were 'missing' from the port INDEX: these were not pkg_added into place, so the package build had to compile them from scratch (a big waste of time and effort), so this is now also a fatal error. PR: ports/85746 (inspired by) [1] Submitted by: Boris B. Samorodov <bsam@ipt.ru> [1]
* Flip from noclean to cleankris2006-02-041-3/+3
|
* Don't bother chowning the client /var/portbuild/, it just takes too longkris2006-02-041-3/+0
| | | | and this doesn't happen in practise unless you screwed up manually.
* Use clean-chroot with clean=2 to remove the chroot instead of duplicatingkris2006-02-041-5/+1
| | | | some of the code
* Flip "noclean" to "clean"kris2006-02-041-3/+3
|
* Instead of passing in a "noclean" boolean, pass in a "clean" level:kris2006-02-041-4/+11
| | | | | | 0 = don't clean chroot 1 = sanitize commonly-modified directories 2 = remove entire chroot
* Also look for chroots that are marked 'dirty' (previous build left chrootkris2006-02-041-1/+5
| | | | in unclean state) and run clean-chroot on them to remove them.
* Don't try to remove the lock file now that we use lockf to manage itkris2006-02-041-2/+0
| | | | Noticed by: linimon
* Fix bogus comments. No code change.linimon2006-02-021-5/+5
|
* Correctly set SRCBASE; the version inherited from buildenv is wrong forkris2006-01-281-0/+1
| | | | the client chroots.
* Don't try to rsync docs, we no longer need to distribute themkris2006-01-281-1/+0
|
* Update the list of quickportskris2006-01-281-1/+1
|
* Warn if there are duplicate MD5/SHA256/SIZE statements for a single fileedwin2006-01-251-3/+33
|
* Small tool to check the necessary lines in the distinfo files, basededwin2006-01-241-0/+105
| | | | | | | | | | | | | | | on the contents of the distinfo files. # # Small tool to find distinfo with missing MD5/SHA256/SIZE statements, # based on the assumption that if there is one of the MD5/SHA256/SIZE # statements, then there should be all of them (except for SIZE # when MD5/SHA256 is set to IGNORE). # # Usage: distinfochecker [-v] [-d directory] # -v - verbose (print) # -d - use directory instead of /usr/ports #
* Support 7.x INDEX buildskris2006-01-231-16/+37
| | | | | Add a few more local configuration variables Minor cleanups
* Don't bother mounting doc tree, it's not needed by any portskris2006-01-221-12/+8
| | | | | | Use LOCALBASE/X11BASE values from buildenv xorg uses the stock BSD.x11-4.dist now.
* Remove -nodoccvs option, it turns out mounting the doc tree is notkris2006-01-221-14/+1
| | | | required by any ports
* Also clean up linprocfs mountskris2006-01-221-0/+1
|
* Pull in buildenv for LOCALBASE/X11BASE locationskris2006-01-221-2/+4
| | | | Don't bother cleaning up doc mounts, they are not needed.
* Use LOCALBASE and X11BASE from buildenvkris2006-01-221-1/+4
|
* Allow for the possibility of overriding LOCALBASE and X11BASEkris2006-01-221-0/+2
|
* Exit with the correct error code when a make target failskris2006-01-151-3/+3
| | | | | PR: ports/64930 Submitted by: Damir Kiramov <damirycha@damirycha.net.ru>
* Back out last commit, it was the wrong filekris2006-01-151-17/+15
|
* Exit with the correct error code when a make target failskris2006-01-151-15/+17
| | | | | PR: ports/64930 Submitted by: Damir Kiramov <damirycha@damirycha.net.ru>
* Add portsvar.sh schell script into Tools/scripts.daichi2006-01-111-0/+133
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | portsvar.sh - print out variable defined through bsd.port.mk example: % portsvar.sh PORTSDIR OSVERSION PORTSDIR = /usr/ports OSVERSION = 600034 % portsvar.sh -e "PORTS[^_]" PORTSDIR = /usr/ports PORTSSUPFILE = /usr/share/examples/cvsup/ports-supfile % portsvar.sh USE_RUBY=yes RUBY_VER RUBY_ARCH RUBY_VER = 1.8 RUBY_ARCH = i386-freebsd6 % portsvar.sh -w ruby RUBY_VER RUBY_ARCH RUBY_VER = 1.8 RUBY_ARCH = i386-freebsd6 % portsvar.sh -w kde -e KDE_ KDE_MAINTAINER = will@FreeBSD.org KDE_ORIGVER = ${KDE_VERSION} KDE_PREFIX = ${LOCALBASE} KDE_VERSION = 3.5.0 MASTER_SITE_KDE_kde = ${kmaster:S@%SUBDIR%/@@g} % portsvar.sh -a list all variables through bsd.port.mk % portsvar.sh -a -w kde list all variables through bsd.port.mk including kde portsvar.sh is easy tool to check out the variables used in /usr/ports/Mk/bsd.*.mk.
* This script may be run on a client machine to force it to flush its squidkris2005-12-111-0/+15
| | | | | cache. This is useful if the client is holding a bad or stale cached copy of a package that is causing problems for package builds.
* Bump the file size limit to 300MB now that openoffice distfiles exceedkris2005-12-111-5/+5
| | | | 256MB. Clarify a comment.
* Shuffle the order of a cdkris2005-12-111-2/+1
|
* Remove 0-sized entries to avoid misbehaviourkris2005-12-111-0/+4
|
* Don't use a lockfile, the script will be called with lockf -t0 instead tokris2005-12-112-16/+0
| | | | avoid problems with stale lockfiles after a reboot.
* Don't use a lockfile, the script will be called with lockf -t0 insteadkris2005-12-111-6/+0
| | | | to avoid problems with stale lockfiles after reboots.
* Update the list of quickportskris2005-12-111-1/+1
|
* Don't set -nocopy when -norsync is set, otherwise the setupnode scriptkris2005-12-111-1/+1
| | | | doesn't completely prep the client.
* Don't use a lock file, the script will be called with lockf -t 0 instead.kris2005-12-111-6/+0
| | | | This avoids problems from stale lockfiles after reboots.
* Mount the md image async since this gives much better performancekris2005-12-111-1/+1
|
* Utility: A tool to identify similar pkg-descr filesedwin2005-11-261-0/+24
| | | | | | | | | | The ports tree contains many tools with almost-similar names and no helpful pkg-descr difference. The goal of pkg-descr would be to aid the user in his choice of port version. Ergo, similar pkg-descr files are bad. PR: ports/89432 Submitted by: Jonathan <afarsec@012.net.il>
* Remove, don't comment out, unused variableskris2005-10-111-2/+0
|
* Remove unused variables. Don't bother protecting against negativekris2005-10-111-4/+2
| | | | queue lengths since that doesn't arise.
* Update lockf to lockf -k in example usagekris2005-10-111-1/+1
|
* Update the lockf command to add -k in example usagekris2005-10-111-1/+1
|
* When -norsync is set, don't bother to run md5 over the bindist.tarkris2005-10-111-3/+9
| | | | | | | | | | and copy it to the client. This has two benefits: 1) Avoids spamming the master with dozens of md5 processes when dosetupnode is spawned for all client machines at ocne 2) Avoids silly copy attempts on disconnected nodes for which the file is copied to itself
* Change lockf to lockf -k in a commented-out command, just in case it'skris2005-10-111-1/+1
| | | | ever uncommented.
* Add support for use_md_swapkris2005-10-111-0/+5
|
* Add support for use_md_swap. When this variable is set in akris2005-10-111-4/+18
| | | | | | | | | | | | | | | | | | | | | | portbuild.conf, builds will each be done in a separate swap-backed md. This dramatically improves build performance since * Every transaction is not written to disk, so disk bandwidth is not a bottleneck * Multiple builds do not contend with each other for the same set of filesystem locks and other per-device resources The size of the md devices is controlled by the md_size variable. '2g' seems to be a good size. Currently we mdconfig -u each device after each port build, since otherwise dirty blocks accumulate and the md eventually uses a full amount of backing store (2g in the above example). This is a problem if there is unsufficient swap backing to accomodate them all. XXX This should be made configurable to avoid the performance penalty on systems that do have enough swap backing
* No need to hold the queue lock while polling client loadkris2005-10-111-1/+1
|
* * Use lockf -k instead of lockf. If there is ever contention from >1kris2005-10-111-5/+5
| | | | process, you must use -k or lockf can give out two locks at once
* * Add support for use_md_swapkris2005-10-111-12/+22
|
* * Unmount linprocfs around pkg_adding dependencies, to try and workkris2005-10-111-3/+41
| | | | | | | | | | | | | | | around silly failures in some ports when it is present * Add a footer to completed builds that is recognised by pdispatch to retry truncated builds * If ALWAYS_KEEP_DISTFILES is not present in the environment or port makefile, then clean up DISTDIR after the build finishes, to prevent collection of distfiles for this port. * Finish flipping the switch on -noplistcheck - this is activated by passing in the NOPLISTCHECK environment variable instead of using PLISTCHECK in the opposite case
* * Finish flipping the switch on -noplistcheck - this is activated bykris2005-10-111-11/+6
| | | | | | | | | passing in the NOPLISTCHECK environment variable instead of using PLISTCHECK in the opposite case * Remove the unused -nodummy function * Pass in ALWAYS_KEEP_DISTFILES when -distfiles is set
* * Remove support for the unused -nodummy functionkris2005-10-111-65/+66
| | | | | | | | | | | | | * Finish flipping the switch on -noplistcheck - this is activated by passing in the NOPLISTCHECK environment variable instead of using PLISTCHECK in the opposite case * Always pull in the distfiles from the client if they exist (needed for forthcoming ports tree changes to satisfy GPL license requirements) * If the build did not complete "cleanly", e.g. it was interrupted by a network outage or client machine panic, then retry it until it succeeds instead of just leaving a dirty truncated log
* * Remove unused -nodummy argumentkris2005-10-111-34/+6
| | | | | | | | | | | * Finish flipping the switch on -noplistcheck; set NOPLISTCHECK instead of PLISTCHECK in the opposite case * Clean up the distfiles/ directory when starting build, so it is not contaminated by old distfiles * Remove commented-out code to don't back up old distfiles/ directory, it's just too big to do this.
* Silence some possible errors from chflags -Rkris2005-10-111-1/+1
|
* Silence possible errors from some recursive commandskris2005-10-111-2/+2
|
* - Add a new option -L, it works like -l but uses pkg-descr to creategarga2005-10-051-17/+30
| | | | | | commit message. Approved by: will (maintainer)
* Remove some hardcoded values to hopefully stop random users from shootingkris2005-09-091-12/+27
| | | | | | their feet off in public. Suggested by: adamw
* - Handle different INDEX filename on 5.X and abovepav2005-09-051-2/+5
| | | | | PR: ports/85281 Submitted by: Vasil Dimov <vd@datamax.bg>
* Check for extra files on !i386 alsokris2005-07-251-6/+4
|
* Support FreeBSD 7.xkris2005-07-255-5/+15
|
* Drop the removed openoffice 1.0 ports from the quickports listkris2005-07-251-1/+1
|
* Correct typokris2005-07-251-1/+1
|
* Add prototypes for all the subroutines which fixes compilation withmarcus2005-07-111-9/+20
| | | | | | Perl 5.8.7. Reported by: mezz
* Fix typosvs2005-04-181-3/+3
| | | | Approved by: sobomax
* As discussed on the cvs-ports-list, make 'addport' print a warning if the ↵vs2005-04-121-0/+1
| | | | | | | | | directory name contains upper-case characters as it makes finding a port harder. PR: ports/79679 Approved by: will, portmgr(krion)
* Add a splitpatch.pl utility, a small script to convert multi-filetobez2005-04-122-0/+112
| | | | | | patches to several appropriately named single-file patches. Requested by: flz
* - Add bump_revision.pl, a small script to bump the PORTREVISION variableflz2005-04-122-1/+193
| | | | | | | | | | 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
* - Replace pkg-comment with COMMENT to reflect latest (*sigh*) changesflz2005-04-121-2/+2
| | | | | | | | in the ports framework. PR: ports/62767 Submitted by: Igor Pokrovsky <tiamat@comset.net> Approved by: maintainer timeout (> 8 months)
* Use WRKDIRPREFIX instead of hardcoded value.kris2005-04-121-1/+3
| | | | Clean up after we're done.
* Change rsync -l to -L for the tarballs/ directory (so that danglingkris2005-04-031-1/+1
| | | | | symlinks are not created on the target) and rsync the entire directory so that extra files are deleted.
* Build packages with WRKDIRPREFIX=/work (which does not exist bykris2005-04-031-1/+9
| | | | | | | default) instead of /tmp, since some packages incorrectly search this build path at runtime to try to load things. Requested by: nectar
* Increase the nc poll timeout to better deal with network latencies.kris2005-04-031-1/+1
|
* Flip over the -plistcheck switch to -noplistcheck since we now want tokris2005-04-031-5/+5
| | | | make it the default behaviour.
* Update the list of files and directories to filter from the plist checking.kris2005-04-031-1/+3
|
* Checkout Templates from CVS as well since ports with GNU_CONFIGURE willvs2005-03-211-0/+2
| | | | | | need them when building from 'addport -a -t'. Approved by: will
* Put $FreeBSD$ for ident(1)'ing.krion2005-03-131-0/+1
|
* Hopefully last try to fix readmes build.krion2005-03-121-1/+2
| | | | | Submitted by: Christopher Kelley <bsd at kelleycows.com> Pointyhat to: krion
* Fix problems with quoting if PORTSTOP is specified.krion2005-03-101-1/+1
|
* * Add info files to TMPPLIST, only if INFO is specified. [1]krion2005-03-011-1/+1
| | | | | | | | | | | | | | | | | | | | | | | * 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]
* * Instead of using umount -f to unmount things, first use fstat tokris2005-02-121-6/+44
| | | | | | | | | 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.
* Only try to chown the portbuild directory if we are a disconnected clientkris2005-02-121-1/+1
| | | | (i.e. it is not mounted by nfs)
* Instead of using umount -f to unmount things, first use fstat to look forkris2005-02-121-1/+35
| | | | | | | 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.
* * Instead of using umount -f to unmount things, first use fstat tokris2005-02-121-7/+44
| | | | | | | | | | | 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)
* Update the plist checking to look for a subset of files and weed out somekris2005-02-121-1/+6
| | | | false positives.
* Document the check-latest-link and tindex scriptskris2005-01-241-1/+5
|
* Add the script I use to look for duplicate LATEST_LINK entries and tokris2005-01-241-0/+72
| | | | send nag-mails to the responsible maintainers.
* This is the script I use to build indexes for all supported ports branches,kris2005-01-241-0/+164
| | | | | | 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.
* Remove traling spaces.krion2005-01-0928-52/+52
|
* Always set up the bindist-${hostname}.tar file since it's usually small.kris2005-01-071-1/+1
| | | | | | This should probably be changed to only update it if it changes. Approved by: portmgr (self)
* Unset the __MAKE_CONF variable after setting up buildenv, because wekris2005-01-071-0/+3
| | | | | | want to use the default value in the build chroot. Approved by: portmgr (self)
* Allow machines to use an alternate address for polling for job load (e.g.kris2005-01-071-1/+3
| | | | | | | 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)
* * Include portbuild.conf before portbuild.${hostname} to reset the defaultkris2005-01-071-4/+6
| | | | | | | | value of variables * Allow krion to drink from the email firehose Approved by: portmgr (self)
* * The mlist file now only has one field per line.kris2005-01-071-4/+9
| | | | | | | | * Correctly calculate job concurrency in pass two as well * In pass two run dosetupnode -rsync to avoid wasting time. Approved by: portmgr (self)
* krion wants to drink from the pointyhat email firehose as well.kris2005-01-071-1/+1
| | | | | | XXX This should be a portbuild.conf tunable Approved by: portmgr (self)
* Now that I have so many remote build machines, don't force trying tokris2005-01-071-7/+0
| | | | | | | | 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)
* * Support the -norsync argument to only remove the existing build chrootskris2004-12-281-2/+8
| | | | | | | | | | | | | | | | | 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.
* * It does in fact make sense to specify -incremental and -noindex at thekris2004-12-281-7/+7
| | | | | | | | | | 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
* Fix the Xvfb code to run Xvfb before the build phase if detectedkris2004-12-281-15/+25
| | | | | | | | | | | (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)
* Overhaul of the job scheduler. The new scheduler runs buildskris2004-12-284-29/+119
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Overhaul of the job scheduler. The new scheduler runs buildskris2004-12-281-26/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* * Catch up to change in formatting of 'extra files' section in logskris2004-12-281-4/+3
| | | | * Other minor changes
* /rescue/mount_linprocfs isn't functional when called bykris2004-12-281-1/+2
| | | | | | | | | /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.
* Support 5-exp buildskris2004-12-284-4/+14
|
* Use X_WINDOW_SYSTEM for 4.x builds too.kris2004-12-101-2/+2
|
* Belatedly catch up to XFREE86_VERSION -> X_WINDOW_SYSTEM change; applykris2004-12-101-3/+3
| | | | the BSD.x11.dist if set to xfree86-3, otherwise use BSD.x11-4.dist.
* The explanations of each build error no longer live on bento, they livelinimon2004-12-092-7/+7
| | | | on pointyhat.
* Construct permanent links to the error logs here too.kris2004-12-051-4/+4
| | | | | Submitted by: linimon Reminded by: marcus
* Copy the statically-linked binaries from /rescue on the host, insteadkris2004-12-051-4/+11
| | | | | of needing to also include the dynamic libraries that were confusing some ports. We still need libc.so.[56] for killall to work, though :(
* Be silent about attempts to unmount filesystems from within the chrootkris2004-12-051-4/+4
|
* Clean up the symlink in ${pb}/${arch}/${branch}/latest/${dir} when we findkris2004-11-251-0/+5
| | | | a port that should not be listed here
* If sudo_cmd is set, assume we need to chown the files we created onkris2004-11-251-0/+3
| | | | the client to the client_user so they can later write to them
* Rework the -incremental support slightly; this should now be robust enoughkris2004-11-251-3/+5
| | | | to use.
* Catch up to the changed format of the logs.kris2004-11-251-4/+4
| | | | | | | List the extra/removed/changed files separately, and colour-code the serious errors (files left behind outside of /usr/local and /usr/X11R^; files removed that were installed by another port, and files with changed permissions or ownership)
* * Recursively list all files detected as having been left behind afterkris2004-11-251-7/+22
| | | | | | | the port deinstall; mtree does not recurse into subdirectories it does not know about * Break out the 'files incorrectly removed' and 'files incorrectly changed' into their own sections
* * Fix INDEX build if MAINTAINER is not defined. [1]krion2004-11-191-0/+47
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * Remove USE_QT2 since it's obsolete now. [2] * Clarify comments about ARCH. [3] * Speedup 'make readmes'. Add a perl script "Tools/make_readmes" and modify bsd.port.subdir.mk to avoid recursing into individual port directories to create README.html. [4] * Fix 'make search' to allow case insensitive search on 5-x/6-x. [5] * Add the possibility to search the ports by category. [6] * Remove tk42 and tcl76 from virtual categories since they're obsolete. [7] * Introduce new variable - DISTVERSION, vendor version of the distribution, that can be set instead of PORTVERSION and is automatically converted in a conforming PORTVERSION. [8] * Use --suffix instead of -b option for patch(1) to make it compatible with BSD patch(1) [9] * Fix {WANT,WITH}_MYSQL_VER behavior, to deal with conflicting versions. [10] PR: ports/68895 [1], ports/69486 [2], ports/68539 [3], ports/70018 [4], ports/68896 [5], ports/73299 [6], ports/73570 [7], ports/67171 [8], ports/72182 [9] Submitted by: linimon [1][3], arved [2][7], cperciva [4], Matthew Seaman <m.seaman@infracaninophile.co.uk> [5], Radek Kozlowski <radek@raadradd.com> [6], eik [8], Andreas Hauser <andy-freebsd@splashground.de> [9], clement [10]
* Newline should go after the terminating punctuation (fix typo).dd2004-11-071-1/+1
| | | | Approved by: will
* Fix a couple of bugs in the extraction of this from dopackages, andkris2004-10-251-33/+20
| | | | | flatten the setupnode() function into the main body since it's only called from one place.
* Redefine the -norestr option to mean 'don't build the list ofkris2004-10-251-78/+73
| | | | | | | | | | restricted ports' instead of 'don't build any restricted ports' since the former is useful when we're not intending to publish the results of a build, but the latter is not. Move the build preprocessing (directory setup, old build rotation, etc) out from under -nobuild, so that we can set up a new build using that option.
* If the symlink under latest/ exists, then use that to find the most recentkris2004-10-251-1/+6
| | | | | error log for the port, instead of assuming it exists in the current build.
* We now also do 6.x builds in the '6' branch.kris2004-10-251-3/+3
|
* Use the absolute path to nc(1) to deal with it not being in the PATH.kris2004-10-251-3/+1
| | | | Remove useless sleep(1).
* Clean up the 'latest error log' symlink when the build is successful.kris2004-10-251-0/+4
|
* When a port build fails, create a symlink to the error log underkris2004-10-251-3/+4
| | | | | | | ${arch}/${branch}/latest/${portdir}. We will use this in the processfail script, so that the "new package build errors" webpages do not have out-of-date links but instead link to the most recent copy of the build error.
* Strip out date/time from +++/--- headers in generated patchfiles, so that theysobomax2004-10-141-11/+12
| | | | don't generate extra hunk each time patchfile is updated.
* Support ${client_user} and ${sudo_cmd} for running commands as root onkris2004-09-271-1/+5
| | | | | | | machines where we first connect to a non-root user and then increase privileges. Approved by: portmgr (self)
* * Break out setupnode into the dosetupnode script so it may be calledkris2004-09-271-37/+3
| | | | | | | | manually * Support 6.x builds Approved by: portmgr (self)
* Break out the setupnode function of dopackages into a separate script sokris2004-09-271-0/+47
| | | | | | | | | | | | | | | that it may be called by hand. Support new portbuild.conf variables client_user = user to connect to on the client (not necessarily root). This user must have write permission to the /var/portbuild tree if disconnected=1 (i.e. we're going to run rsync). rsync_gzip = set to "-z" to enable compression on low-bandwidth disconnected clients. Approved by: portmgr (self)
* * Bail out if we can't claim a chroot directory in the client (e.g. ifkris2004-09-271-13/+17
| | | | | | | | | | | | | | | ssh times out) * Support new portbuild.conf settings: client_user = user to connect to on the client (not necessarily root) sudo_cmd = If ssh'ing to a non-root user, run this command to gain root privs (set to empty string for client_user=root, or sudo for !root). Cannot require interactivity, of course. Approved by: portmgr (self)
* Refuse to "clean" / if something goes wrong upstream and we are passedkris2004-09-271-0/+5
| | | | | | the wrong path Approved by: portmgr (self)
* Pull in portbuild.$(hostname) for per-client customizationkris2004-09-271-1/+3
| | | | Approved by: portmgr (self)
* Support 6.x buildskris2004-09-272-1/+5
| | | | Approved by: portmgr (self)
* * Support 6.x buildskris2004-09-271-2/+12
| | | | | | | * Default 4.x to XFree86 4.x, 5.x and above to x.org * Don't pick up local customizations from OPTIONS Approved by: portmgr (self)
* Use a consistent PATH in both portbuild and dopackages.marcus2004-08-281-1/+1
|
* Avoid possible GNATS timeouts by using query-pr.real direclty.krion2004-07-281-1/+1
|
* Clean up the specified chroot (umount filesystems, and scrub thekris2004-07-141-0/+36
| | | | directories likely to contain changed files).
* Atomically claim an unused chroot directory. The previous algorithmkris2004-07-141-0/+52
| | | | | was not atomic and could have ended up with two port builds trying to use the same chroot. Report the claimed directory back to the caller.
* Bump up the cleanup timeout to directories that have been in use forkris2004-07-141-3/+3
| | | | >48 hours, to cope with monster ports like openoffice and atlas.
* Back out the attempt to list the error type in the failure summary;kris2004-07-141-14/+1
| | | | | | | because this file is a chronological history of port builds that have failed, the files listed may not be present in the current set of error logs, and we currently have no easy way to find the most recent failure log to use instead.
* Generate permanent URLs in the error reports. The directories likekris2004-07-141-1/+10
| | | | | | | | i386-5-latest that are linked to from the index.html are symlinks to dated directories (e.5.`date`), so the URLs in the error reports will expire with the start of the next build when the symlink is repointed. This change makes the URLs in the error reports use the realpath of the target file, so they do not expire.
* * Add support for ${TRYBROKEN}.kris2004-07-141-6/+67
| | | | | | | | | | | | | | | | | | | | * Clients no longer have ssh access to the master, so we need to push/pull everything on the client from here. This means we need to know where the build took place so we can go in and get the files after it finishes. Introduce the claim-chroot script which atomically claims a free chroot directory on the host and returns the name. This directory is later populated by the portbuild script if it does not already contain an extracted bindist. * Use the per-node portbuild.$(hostname) config file to decide where in the filesystem to claim the chroot on the build host. * If a port failed unexpectedly (i.e. is not marked BROKEN), or if something strange happened when trying to pull in build results from a client, then send me email (XXX should be configurable). * Clean up after the build finishes and we have everything we need, by dispatching the clean-chroot script on the client.
* * Add a cleanup() function and use it so that we archive the ${WRKDIR}kris2004-07-141-68/+122
| | | | | | | | | | | | | | | | | | | if requested (".keep" file in the port directory), no matter where we fail. * Add package dependencies before the corresponding build stage (e.g. FETCH_DEPENDS before 'make fetch'), and remove them again afterwards. This allows us to catch ports that list their dependencies too early/late. * No need to check for set[ug]id files here, the security-check target in bsd.port.mk does it for us. * Exclude some more directories and files from showing up in the mtree before/after comparison, to trim down the false-positive in the pkg-plist check. * Other minor changes
* * Remove the quickports stuff, it didn't (ever?) work as designed andkris2004-07-141-112/+156
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | it's done properly^Wbetter in makeparallel * Script accepts new arguments: -nodoccvs: skip cvs update of the doc tree -trybroken: try to build BROKEN ports (off by default because the i386 cluster is fast enough now that when doing incremental builds we were spending most of the time rebuilding things we know are probably going to fail anyway. Conversely, the other clusters are slow enough that we also usually don't want to waste time on BROKEN ports). -incremental: compare the interesting fields of the new INDEX with the previous one, remove packages and log files for the old ports that have changed, and rebuild the rest. This substantially cuts down on build times since we don't rebuild ports that we know have not changed. XXX checkpoint of work-in-progress, not yet working as committed. * When setting up the nodes, read in per-node config files ("portbuild.$(hostname)") before dispatching the setupnode script on each node. For disconnected nodes (which don't mount the master via NFS), we also rsync the interesting files required by the builds (ports/src/doc trees, bindist tarballs, scripts) into place on the client. They will be mounted locally via nullfs in the build chroots. * Break out the restricted.sh generation into a makerestr script so it can be called manually as needed. * Remove the -nocvsup argument which has been unused for a long time. * For now, don't prune the list of failed ports with prunefail, since when -trybroken is not specified, every BROKEN port ends up in the duds file (so the build is skipped), and as a result we would prune almost everything from the list of failed ports. XXX prunefailure should be run conditionally on -trybroken, or I should find a way to prune in both cases. * Don't run index in the background, it was thrashing against makeduds and not saving any time by doing it concurrently. * Build with 'make quickports all' to kick off the quickports builds earlier. * Delete restricted and/or cdrom distfiles *after* post-processing the distfiles, otherwise the script doesn't remove any of them since they're not in the expected place. * Miscellaneous other minor changes and cleanups
* Parse the slightly-different format of the build logs.kris2004-07-141-1/+1
|
* Parse the slightly-different format of the build logs.kris2004-07-141-3/+3
|
* * Accept another argument, the value of the disconnected variable thatkris2004-07-141-25/+25
| | | | | | | | | | | | | | | | | | | | | | | tells us whether the node has NFS access to the master. * Also copy the bindist-$(hostname).tar file to allow local customization of the build chroots (e.g. resolv.conf and make.conf files for disconnected systems) * For disconnected hosts, we don't copy the bindist files from the master, but just set up the local directories and let the server rsync them into place later. Also set up dangling symlinks to the bindist files in the build area, which will be filled in by the server too (in the NFS case it makes sense to cache the bindist files locally to avoid extra NFS traffic, but here we know the file is local so a symlink is fine) * Remove an apparently spurious 'killall fetch' that snuck in for what were probably transient reasons. * Forcibly clean up old chroot directories since we are preparing to start another build and don't want old (possibly orphaned) builds to skew the job scheduling or use up resources.
* Allow local customization of the node using the portbuild.$(hostname) file.kris2004-07-141-0/+1
|
* Send me mail when a previously-broken port builds successfully.kris2004-07-141-2/+5
| | | | XXX Should not be a hard-coded address
* * Initial support for disconnected nodes (not on same LAN as buildkris2004-07-141-83/+88
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | host), specified by disconnected=1 in portbuild.$(hostname) file. These do not mount via NFS, so we need to maintain a local copy of things needed by the build (like the ports/src/doc trees) on the build host, which are mounted into the chroot by read-only nullfs. These local files are maintained in the dopackages script via rsync. * Download packages via http instead of NFS. Allow fetching via a local http proxy (http_proxy variable in per-node portbuild.$(hostname) file). Caching package dependencies saves about 85% of package fetches and similar reduction in package fetch traffic by byte count. * Support a per-node tarball (bindist-$(hostname).tar) to customize the build chroots. This is used for things like local resolv.conf and make.conf files on disconnected nodes. * Make sure we don't use a chroot until it is finished extracting. * Don't set '.' in PATH; this is bad practise, and fortunately nothing seems to rely on it. * Only try to build broken packages if requested * Try harder to unmount leftover linprocfs mounts in the chroot, by copying in the 5.x mount binary and supporting libraries from the host system. The 5.x mount is able to unmount by FSID in situations where the 4.x umount becomes confused. * Don't clean up when we are signalled, that is done by the build master from outside. * Suppress some code relating to jail builds, which are not yet ready for use. * Don't push results of the build back to the master; the master now pulls them from the client when the build completes. Clients no longer need ssh access into the master; this is good for security as well as significantly reducing the load on the master since it is not thrashed by dozens of sshd processes.
* Hack around the sparc64 64-bit time_t test in 'installworld' sincekris2004-07-141-0/+1
| | | | | we're installing (into a temporary staging area) on a non-sparc64 machine that does not have 64-bit time_t.
* * Break out the 'parallel' target from /usr/ports/Makefile. Onekris2004-07-141-6/+40
| | | | | | | | | | | | | | | | | | | | | | advantage is that here we know the value of PKGSUFFIX (.tgz/.tbz) for the build via buildenv. * Add a list of 'quickports', which are ports with long dependency chains that we should kick off straight away to try and avoid bottlenecks later on when most of the cluster idles waiting for one or two ports to build. Ideally we'd build dependencies of these ports exclusively first and only build other ports when we run out (i.e. a build slot becomes free), but I couldn't work out how to do this. As a compromise, we now do 'make -k -j<#> quickports all' which doesn't give quite as high a priority to the quickports (i.e. we also build other ports from the beginning while there are quickport dependencies still to build), but is better than nothing. * Pass in the FETCH/EXTRACT/PATCH/BUILD/RUN_DEPENDS separately via env variables when dispatching a job. This allows us to add and remove the dependencies at the corresponding build stage to catch ports with dependencies listed too early/late.
* Set INDEX_JOBS to control index build concurrencykris2004-07-141-0/+3
|
* Drop the ignorelist concurrency back to 1 because I'm occasionally seeingkris2004-07-141-1/+1
| | | | | overlapping I/O. Something similar to how parallel index builds are now done will need to be done here too.
* * If we time out connecting to a machine, give it a weight of 999 to makekris2004-07-141-2/+2
| | | | | | | sure we don't try and schedule jobs on it even if all other machines are busy * Remove sleep in outer loop, this isn't needed or worthwhile now that there are so many machines being monitored
* Chase bento to pointyhatkris2004-07-141-1/+1
|
* * Be even more explicit about partial ports trees being unsupportedkris2004-07-141-13/+62
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | for INDEX builds [1] * Remove the parallel target from Makefile; this is heavily tied to the package build cluster and can be better done in the makeparallel script (commit to follow) [2] * Extend the format of INDEX to separately list the EXTRACT/PATCH/FETCH_DEPENDS instead of lumping them all in together with BUILD_DEPENDS. The three new fields are appended to the end of the record in that order. [2] * Change BROKEN to IGNORE in BROKEN_WITH_MYSQL failure code [3] * Support non-default PREFIX for perl 5.00503 [5] * Use pkg_info -I instead of ls when searching for conflicts [6] * Allow local customization of the port subdirectories by including ${.CURDIR}/Makefile.local in bsd.subdir.mk if it exists [7] * Fix 'make search' when ${PORTSDIR} is a symlink to a directory name containing extended regexp metacharacters [8] Submitted by: linimon [1] [3], kris [2], lth [4], sem [5], eik [5] [6], Roman Neuhauser <neuhauser@chello.cz> [7] PR: 68299 [1], 67705 [3], 67264 [4], 59696 [5], 66568 [6], 68072 [7]
* Modernize these two scripts a little bit to make it easier to dealmurray2004-06-092-6/+16
| | | | | | with 5.X or 4.X package sets (i.e., INDEX vs INDEX-5 and tgz vs tbz) OKed by: marcus
* Hack in master/slave supporteik2004-06-051-27/+69
|
* Add dopackages.wrapper, a wrapper script around dopackages that sets upmarcus2004-06-031-0/+53
| | | | | | | | | | | | build locking, log files, and cleans things up if a build fails. This script is the primary starting point for a package build. Symlinks should be created in the form of dopackages.${branch} -> dopackages.wrapper where ${branch} is currently one of 4, 4-exp, or 5. This script takes the place of the unofficial (i.e. uncommitted) dopackages.steveX scripts. Ok'd by: kris Tested by: 4.10-RELEASE package build
* parse $FreeBSD$ with yyyy-mm-dd format dateseik2004-05-311-1/+1
|
* protect $FreeBSD: ... $ from being expandedeik2004-05-301-1/+1
| | | | Noticed by: mat
* don't terminate the log entry with the first hypheneik2004-05-301-1/+1
|
* - make somewhat more robust against a corrupted ports treeeik2004-05-301-30/+80
| | | | | | | | | | - CC committers and maintainer [1] - include affected ports in the subject line [2] - do a CVS log of the version checked out [3] Suggsted by: Ade Lovett <ade@FreeBSD.org> [1] Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net> [2] Pav Lucistnik <pav@FreeBSD.org> [3]
* - Remove 'pkg-plist' from required fileskrion2004-05-271-2/+1
| | | | Approved by: sobomax
* - fix a bug handling the maintainer field when ALLPORTS is usedeik2004-05-221-35/+56
| | | | | | - add an option to watch for maintainer changes - change watch regex to match PKGORIGIN, not PKGNAME
* Turn chkversion into an all-dancing, all-singing notification tool.eik2004-05-191-35/+138
| | | | | | | | You can even get notified of version changes in your favourite perl modules by setting WATCH_REGEX='p5-.*' Plus, it has a nice configurable nagging option.
* small optimazation: don't compare versions that are equaleik2004-05-181-1/+1
|
* check only ports connected to the build.eik2004-05-181-15/+32
|
* - integrated chkorigineik2004-05-171-51/+102
| | | | | | - eliminated shell usage [1] Submitted by: mat [1]
* FWIIW, spawn fewer processes.eik2004-05-161-3/+12
|
* support for symlinked portsdir (but no other symlinks in the ports tree)eik2004-05-152-14/+19
| | | | chkversion: support for CVS blame with env CVSBLAME=yes
* add support for ignoring local ports / categories:eik2004-05-151-1/+4
| | | | env 'EXCLUDE=local devel/local' /usr/ports/Tools/scripts/chkmodules.pl
* added chkversion, a script that ensures that PORTVERSIONs don't go backwardseik2004-05-141-0/+155
|
generated by cgit (git 2.34.1) at 2024-11-18 02:56:38 +0800