OpenBSD manual page server

Manual Page Search Parameters

DPB(1) General Commands Manual DPB(1)

dpbdistributed ports builder

dpb [-acemqrRsuUvx] [-A arch] [-b logfile] [-C pathlist] [-D PARAM=value] [-f m] [-F m] [-h hosts] [-I pathlist] [-J p] [-j n] [-L logdir] [-l lockdir] [-M threshold] [-P pathlist] [-p parallel] [-S logfile] [-X pathlist] [pathlist ...]

dpb is used to build ports on a cluster of machines, or on a single machine with several cores. dpb walks the ports tree to figure out dependencies, and starts building ports as soon as it can.

dpb will run with sensible defaults if used without options. Note, however, that it will produce logs, lock files, packages, and package installations. dpb can be restricted to a subset of the tree by giving it pathlist ... to build as parameters.

A pathlist is either a pkgpath(7) to build, or a filename that contains pkgpaths (one per line). pathlist parameters can also take the form filename*scale in order to multiply the weights of all pkgpath(7) in a file by a given scale, or pkgpath=value, in order to set the weight of a given pkgpath(7) to a specific value.

dpb supports ‘hot-fixes’: if a particular port errors out, it is possible to fix the problem, remove the corresponding lockfile, and dpb will pick it up without needing to be stopped and restarted.

In order to build on a cluster, the ports tree itself should be shared through NFS, including distfiles and built packages, but the WRKOBJDIR should be local to each machine.

Also note that logs and locks are managed by the main dpb process, which runs locally, and hence those directories do not need to be shared on the cluster.

Option -h file is used to specify hosts to use, where file may contain lots of information, but can be as simple as a list of hosts to use, one host per line (however, it is recommended to also include a STARTUP script).

Most filenames will go through some control sequence expansions. For instance, the default logdir location can be specified as %p/logs/%a. The following sequences are recognized:

architecture being used.
date at start of dpb, GMtime, formatted as yyyy-mm-dd@hh:mm:ss.
fetch distfiles location (DISTDIR).
hostname running dpb.
logdir location.
portsdir location.
timestamp (number of seconds since January 1 1970) at start of dpb.

Options are as follows:

Build packages for given architecture, selecting relevant hosts from the cluster. By default, the current host's architecture will be used.
Walk the whole tree and builds all packages (default if no pathlist is given).
Explicitly prime the heuristics module with a previous build log, so that packages that take a long time to build will happen earlier. The rolling log under %f/build-stats/%a is automatically used.
Clean port working directory and log before each build.
Don't clean port working directories after build. Only use simple pkgpath(7) in the list, as this does not take subpackages and flavors into account.
Set defined parameter to value. Known parameters are as follows:
Set to 1 if dpb should clean work directories even if the port errored out.
Don't fetch distfiles that are not allowed for cdrom.
Connection timeout for ssh. Defaults to 60 seconds.
Display timeout (in seconds) while waiting for jobs to finish, so that the display is updated even if jobs didn't finish. Defaults to 10 seconds.
By default, dpb will use the BUILD_ONCE optimization (see if run with -a: pseudo-flavors that disable subpackages and are not necessary for bootstrap will be disabled, so that the same port is built once, as far as possible. This flag disables that optimization, which might be desireable if you want to build a small subset of packages which would pull in the kitchen sink otherwise.
By default, dpb will clean old locks from dpb running on the same host that no longer exist, provided they didn't end in error. This is usually the right thing to do after a crash, or after killing dpb abruptly. Sometimes, one may want manual control over which locks to remove.
Alternate way to specify the number of fetch jobs.
Timeout (in seconds) after which fetches that don't show any progress will be killed.
Don't fetch distfiles that are not allowed for ftp.
Don't fetch or build anything. Only run dpb to figure out old distfiles and update ${FULLDISTDIR}/history.
Alternate way to specify the logging directory.
Alternate way to specify the locking directory.
Applicable to fetch modes. If 0, will only fetch normal DISTFILES (default for dpb -f). If 1, will also fetch extra SUPDISTFILES (default for dpb -F).
Make the terminal cursor invisible if possible. Avoids flickering on slow graphics cards.
Disable reading/saving of default build stats under ${DISTDIR}/build-stats/${ARCH}.
Do not update the distfiles history. For instance, if dpb is run a second time after a problem during the first run.
Define a file which will save all terminal output. Mostly useful for presentations, as a way to save dpb output and replay it later at a faster rate. Defaults to %L/term-report.log, can be set to nothing to disable.
Define a start-up script on the command-line, override any host file contents.
Timeout (in seconds * speed factor) after which tasks that don't show any progress will be killed. This can be instead set on a per-core basis as the ‘stuck’ property. Note that this will always be divided by the core's speed factor.
Make dpb call syslog(3) on every task start/end while creating packages. This does produce lots of messages, it is intended to route the logging on another machine, while tracking down panics and other hangs.
Alternate way to specify -s.
The listing job is extra and won't be given back to the pool when it's finished.
Create m jobs for fetching files. Those are separate from the build jobs, since they don't consume cpu, and they run on the localhost. Defaults to 2. Can be set to 0 to bypass fetching jobs entirely, and reduce dpb memory footprint by a lot.
Fetch-only mode, for mirroring hosts. Do not build any package but fetch everything, disregarding BROKEN and ONLY_FOR_ARCHS information. Create m localhost jobs for fetching files.
File with hosts to use for building. One host per line, plus properties, such as:
espie@aeryn jobs=4 arch=i386

Lines starting with a known variable name such as

can also be set inside a configuration file, to reduce the number of options you must pass on the command line.

The special hostname DEFAULT can be used to preset defaults. It should be used at the start of the file.

Use localhost to specify the local machine. dpb will special-case it and not use ssh(1) to connect.

Properties are as follows:

Architecture of the concerned host. (there should be a startup task to check consistency, but currently this has to be set manually on heterogeneous networks.)
Set to 0 or 1 on per-host basis. See ALWAYS_CLEAN parameter.
Chroot to dir before building (only available for distant hosts currently).
Use user for non sudo jobs on distant host (defaults to whoami(1) value).
Number of jobs to run on that host, defaults to hw.ncpu.
Junk unused packages each n steps. See -J option.
Build everything below that wrkdir threshold with USE_MFS=‘Yes’, assuming the ports tree has been configured so that WRKOBJDIR_MFS points to a memory filesystem. thr is the sum, in KBytes, of ports that will be allowed to build in memory. dpb understands suffixes, such as -M 2G or -M 500M.

Note that you should always allow for some margin, as dpb makes its decision based on the size information collected during previous builds, so in cases of significant updates, the work directory size will usually grow. Defaults to 1. During the junk stage, run pkg_delete(1) with the -q (no checksum) option.

Run big ports on several cores. See -p option.
Defaults to 1. Run pkg_add(1) with the repair option. This is useful on some bulk machines which tend to crash a lot, leaving /var/db/pkg in a weird state.
Speed factor. An estimate of that machine's speed with that number of jobs compared to other machines in the same network. Works better with small values, in the range of 1..50. The machine (or machines) with the highest speed factor will get access to all jobs, whereas other machines will be clamped to stuff which does not take too long. Requires previous build information to be effective.
Small threshold (in seconds * sf): ports known to build under that duration are deemed to be small, so dpb won't bother calling fine-grained steps for patch/configure/fake. It will go straight to build and package instead. Defaults to 120 seconds.
Number of squiggles on this host (see ‘the squiggle heuristics’ below). Defaults to 1 squiggle for hosts with 4 jobs or more, 0.7 for hosts with more than 1 job, 0 for single job hosts.
Stuck timeout (in seconds * sf) after which tasks which show no progress will get killed.
Defines a specific connection timeout for ssh to that host.

There are no fine-grained options to control ssh(1) options, as those can be specified through virtual host declarations in ssh_config(5).

List of pkgpath(7) to install, on the local box. This will also add them to the list of things to build.
Override value for the “junk” property. Delete unneeded installed packages during the build. Each prepare stage is followed by a show-prepare-results stage. After every p new dependencies, it will be followed by a junk stage which uses pkg_delete(1) with the -aXI options to delete automatically installed packages that are currently not needed.

dpb keeps track of list of dependencies on a given host, by storing each dependency list in the lockfile corresponding to the package being built.

There is a potential race condition between the depends and junk stage, which dpb solves by preventing more than one job on a given host to be in the depends ... junk stages at one time, by using a per-host lock.

Defaults to 150. Can be disabled by setting to 0.

Some ports, most notably cmake-based, have an annoying dependency handling bug: they compute their makefile dependencies based on all include files present, not just the ones that are actually enabled. Those ports' build may be broken by a junk phase that removes some unused includes that were added as makefile prerequisites. Those ports should be annotated with DPB_PROPERTIES = nojunk until that bug is fixed: while a port with the ‘nojunk’ property is building, junk will be postponed.

Those ports will be marked with a ‘!’ in the display, to make it more obvious why junk seems to be ineffective.

Note that the ‘nojunk’ property is still active for ports in error, in the belief that trivial fixes can be made that will allow the port build to finish.

Number of jobs to run on a single host (defaults to hw.ncpu).
Choose a log directory. (Defaults to ${PORTSDIR}/logs/${ARCH}).
Choose a lock directory. (Defaults to ${PORTSDIR}/logs/${ARCH}/locks). Override to keep local, as locks don't really like NFS.
Build ports below the memory threshold under a memory filesystem, as configured through WRKOBJDIR_MFS (see threshold is the sum, in KBytes, of ports allowed to build there.
Force tty-style reporting.
Read list of pkgpath(7) from file.
Override value for the “parallel” property.

Run big jobs on several cores on the same host, by using MAKE_JOBS=k .

Once such a job has started, dpb will not start new jobs on the same host until the big job has stolen enough cores from other finishing jobs.

Only big ports which are safe for parallel building (annotated with DPB_PROPERTIES = parallel in their Makefile) will be affected.

It is advisable to set k to an integral fraction of the number of cores available on a given host. parameter can be an integer, or of the form ‘/n’, in which case, dpb will set k to a fraction of the total number of jobs on the machine, but never below 2.

Defaults to ‘/2’.

Don't quit while errors/locks are around.
Random build order. Disregard any kind of smart heuristics. Useful to try to find missing build dependencies.
Rebuild existing packages based on discrepancies between the package signature and what the port says it should be. Concretely, use to run a partial bulk build after some library change.

Note that -R won't always work, as rebuilding a package when another version is already installed is not supported.

Read logfile as an initial workdir size log.
Compute workdir sizes before cleaning up, and stash them in log file %L/size.log. Also maintain a rolling log of build sizes under %f/build-stats/%a-size. In order to save time, dpb will actually not always compute new sizes for known directories, but mostly for new ones, or when the package name changes.
Update existing packages during dependency solving. Can be used to run a bulk-build on a machine with installed packages, but might break a bit, since some packages only build on a clean machine right now.
Insist on updating existing packages during dependency solving, even if the new package apparently didn't change.
No tty report, only report really important things, like hosts going down and coming back up, build errors, or builds not progressing.
Read a list of pkgpath(7) from file, and pass them along in the junk phase: those are packages that should stay on the machine if they've been installed by a dependency. Can be used to avoid endlessly removing/reinstalling the most common packages, e.g., devel/gmake.

dpb figures out in which order to build things on the fly, and constantly displays information relative to what's currently building. There's a list of what is currently running, one line per job. Those jobs are ordered in strict chronological order, which means that long running builds will tend to percolate to the top of the list. Normal jobs look like this:

www/mozilla-firefox(build) [9452] 41% unchanged for 92 seconds

This contains:

And fetch jobs look like this:

<dist-3.0.tgz(#1) [4321] 25%

This contains:

This is followed by a host line, containing the name of each host used by dpb. Host names may be tagged with kde3 or kde4. They are followed by a ‘`-'’ for unresponsive hosts, and the pid of the ssh master for distant hosts.

This ends with a summary display:

number of built packages that can be installed.
number of built packages, not yet known to be installable, because of run depends that still need to be built.
number of packages in the queue, e.g., stuff that can be built now, assuming we have a free slot.
number of packages to build, where dependencies are not yet resolved.
number of distfiles to fetch, when -f is used.
number of ignored packages. Details in engine.log.
list of packages that cannot currently be built because of locks.
list of packages in error, that cannot currently be built.
list of packages that haven't shown up yet, usually due to nfs, but watch out for revision bumps.

If those three lists are empty, they won't even show up. Packages in errors may be followed by a ‘!’ if they prevent junk from happening.

Note that those numbers refer to pkgpaths known to dpb. In general, those numbers will be slightly higher than the actual number of packages being built, since several paths may lead to the same package.

dpb uses some heuristics to try to maximise the queue as soon as possible. There are also provisions for a feedback-directed build, where information from previous builds can be used to try to build long-running jobs first.

Similarly, fetches will use the continue option of ftp(1), since distfiles are checksummed after the fetch anyways.

However, on machines with lots of cores, the basic scheduling heuristics yields a tail of very small jobs, where dpb will mostly wait on pkg_add(1) to solve dependencies. Starting with OpenBSD 5.5, a new mechanism (squiggles) was introduced to counter-balance this effect: big machines devote some of their cores to ‘squiggles’, jobs that walk the queue in reverse, thus building smallest ports first. As a result, small ports are built as a trickle alongside the largest ports, thus offsetting the negative effect of the exponential queue for a large part.

Note that ‘squiggles’ can be a non-integral value, usually lower than 1, in which case they represent the fraction of cores that should be affected to squiggles, as decided randomly at the start of each build. 0.7 or 0.8 might be a good choice for dual core machines.

dpb still uses the normal ports tree mechanism while building, which includes LOCKDIR. When starting up dpb will normally detect stale locks from old dpb runs, and remove them. If this does not happen, builds will stay stuck in their initial stage, that is: show-prepare-results, patch, build depending on the port. A telltale message ‘Awaiting lock ...’ can be found in the corresponding logfile paths/pkgpath.log

In addition, when building a package, dpb produces a lockfile in the locks directory, whose name is deduced from the basic pkgpath with slashes replaced by dots. This lockfile is filled with such info as the build start time or the host, or the needed dependencies for this pkgpath.

The lockfile will also contain the name of a parent pkgpath, for paths that were discovered as dependencies. This is particularly useful for bogus paths, where it would be hard to know where the path came from otherwise.

At the end of a successful build, these lockfiles are removed. The lock will stay around in case of errors. (raw value from wait(2)), and the name of the next task in the build pipeline (with todo=<nothing> in case of failure during clean-up). Normal list of tasks is: depends prepare fetch patch configure build fake package clean.

At the end of each job, dpb rechecks the locks directory for existing lockfiles. If some locks have vanished, it will put the corresponding paths back in the queue and attempt another build.

This eases manual repairs: if a package does not build, the user can look at the log, go to the port directory, fix the problem, and then remove the lock. dpb will pick up the ball and keep building without interruption.

It is perfectly safe to run several dpb in parallel on the same machine. This is not optimal, since each dpb ignores the others, and only uses the lock info to avoid the other's current work, but it can be handy: in an emergency, one can start a second dpb to obtain a specific package right now, in parallel with the original dpb.

Note that dpb is very careful not to run two builds from the same pkgpath at the same time, even on different machines: in some cases, MULTI_PACKAGES and FLAVOR combinations may lead to the same package being built simultaneously, and since the package repository is shared, this can easily lead to trouble.

Handling of shared log files and history is also done very carefully by systematically appending to files or using atomic mv operations.

For obvious reasons, this won't work as well with masters running on distinct machines sharing their logs through NFS.

dpb now maintains a list of pkgpath-per-host that are currently building in the affinity directory of its log directory, along with building-in-memory status.

That information is only wiped out when a given build finishes successfully.

Otherwise dpb will try to restart that build on the same host, which can be handy if you interrupt dpb while it is building a large port, or if you remove a lock after fixing a problem.

Currently, kde3 and kde4 can't be built simultaneously. Conflicting ports have been annotated with DPB_PROPERTIES=tag:kde3 , DPB_PROPERTIES=tag:kde4 respectively.

dpb now keeps track of those tags, and will postpone ports with the wrong tag while a given host is used by the other tag.

This heavily relies on the junk stage to clean-up hosts periodically, and it can even forcibly provoke a junk stage even if junk=0.

In order for builds to proceed gracefully, machines should start in a clean slate, without kde3 or kde4 installed.

As a special-case, failing ports with a kde3 or kde4 tag will not interfere with clean-up, so that hosts do not get locked down to a specific tag. This also means that their dependencies may vanish before human intervention addresses the problem.

This is supposed to be a temporary hack, as kde4 is large and having official packages helps a great deal in debugging it.

dpb periodically checks for a file named stop in its log directory. If this file exists, then it won't start new jobs, and shutdown when the current jobs are finished unless -q.

dpb also checks for files named stop-<hostname> in its log directory. If such a file exists, then it won't start new jobs on the corresponding machine.

Apart from producing packages, dpb may create temporary files as ${FULLDISTDIR}/${DISTFILE}.part.

In fetch mode (-f and -F), dpb populates ${FULLDISTDIR}/by_cipher/sha256 with links. It also uses ${FULLDISTDIR}/distinfo and ${FULLDISTDIR}/history as a ‘permanent log’:

cache of distfiles checksum. Contains all sha256(1) checksums of known files under ${FULLDISTDIR}. Fetching uses this to avoid re-checksumming known files.
Log of old files under distinfo. After successfully scanning a full ports tree (dpb -a), the fetch engine knows precisely which files are needed by the build (and their checksums). Anything that is
  • recorded in distinfo but unneeded
  • recorded in distinfo but with the wrong checksum
  • not recorded in distinfo, but not needed
will be entered at the end of history as a line:

ts SHA256 (file) = value

with ts a timestamp from Unix epoch.

When cleaning up old files, with a tool such as clean-old-distfiles(1), it is vital to check both the checksum and the file name: since mirroring stores permanent links under by_cipher, files which are still needed will appear in history under their old checksums, as an indication the link should be removed, but possibly not the file itself.

If ${DISTDIR} ever becomes corrupted, removing ${DISTDIR}/distinfo will force dpb into checking all files again.

dpb also records rolling build statistics under ${DISTDIR}/build-stats/${ARCH}, and uses them automatically in the absence of -b logfile.

If -s is used, size information for successful builds will be recorded under ${DISTDIR}/build-stats/${ARCH}-size (by default, location adjustable with -S sizelog). This is then reused for the mfs threshold option.

dpb will also create a large number of log files under ${PORTSDIR}/logs/{$ARCH}:

Affinity information. One file per full pkgpath, with slash replaced by dots like so: affinity/lang.ghc,-main.
On startup dpb reads existing affinity information, and records it in that log, together with its pid. This log just exists to verify, along with engine.log, whether correct affinity was heeded.
This is purely for gathering performance statistics, about how much lock contention happened around pkg_add(1) and usage. Plotting cumulated time may help in fine-tuning squiggles parameters.
Actual build log. Each line summarizes build of a single pkgpath, as: ‘pkgpath host time logsize (detailed timing)[!]’ where time is the actual build time in seconds, host is the machine name where this occurred, logsize is the corresponding log file size, and a ! is appended in case the build didn't succeed.

The detailed timing info gives a run-down of the build, with clean, fetch, prepare, patch (actually extract+patch), configure, build, fake, package, clean detailed timing info. Note that the actual build time starts at ‘extract’ and finishes at ‘package’.

Paths that do not clean correctly, and required sudo to clean the directory.
Shows the actual concurrency achieved as a result of job starvation / parallel handling. Only gets a new line when the value changes: pid timestamp jobs
List of pkgpath frequencies, filled at end of LISTING if -a. Will be automatically reused when restarting a build: a quick LISTING of the most important dependencies will happen before the general LISTING.
Log of the ftp(1) process(es) that attempted to fetch the distfile.
Build engine log. Each line corresponds to a state change for a pkgpath and starts with the pid of dpb, plus a timestamp of the log entry.
pkgpath temporarily put aside, because a job is running in the same directory.
pkgpath ignored, either directly, or indirectly because a dependency was ignored. End of the line states reason why ignored.
affinity mismatch: path considered for build, but not the right host, followed by the affinity information.
pkgpath built / distfile found.
forcible clean-up before building a port with a kde tag.
error in build or fetch.
distfile queued for download.
package still not found due to nfs on this run.
pkgpath can be installed.
job to build pkgpath started. Also records the host used for the build.
kde mismatch, no build until host has been cleaned up.
job did not start, existing lock detected.
job did not finish. The host may have gone down.
built package is no longer required for anything.
pkgpath queued as buildable whenever a slot is free.
pkgpath to build / distfile to download.
pkgpath put back in the buildable queue, after job that was running in the same directory returned.
affinity mismatch, but job will start on the wrong host anyways, as the queue contains no other buildable path.

Please note that the engine is no longer run after each package build event because of performance considerations, so the ‘Q’ and ‘I’ changes may be delayed by a few ‘B’.

Lists of equivalent pkgpaths for the build, when default flavors and default subpackages have been resolved.
List of URLs that did not lead to a correct distfile, either because they were not responding, or because of incorrect checksums.
List of URLs that fetched correctly, along with timing statistics.
List of pkgpaths that require manual intervention, in human-readable form.
Complete library signature of the host.
Option -J counts the number of dependencies directly added to decide when to run pkg_delete -a. This file sums up how many ports were built, and how many ports had dependencies each time dpb decides to junk.
Directory where locks are created. The slash in a pkgpath is replaced with a dot like so: locks/devel.make to flatten the structure.
list of needed dependencies at each point in time for each host when the -J option has been used.
one file or symlink per pkgname.
one file or symlink per pkgpath.
Some parts of dpb are computationally intensive, such as the engine runs to determine new stuff that can be built, and the actual display reports.

Both those activities are rate-limited, so that dpb doesn't run its engine at each new package build, and doesn't update its display every time there is a phase change.

Lines tagged with ‘ENG’ correspond to the engine; lines tagged with ‘REP’ correspond to the display reports.

Lines ending with a dash ‘-’ correspond to new activity that didn't trigger a computation.

Other lines will feature a plus ‘+’ for normal runs, or an exclamation point ‘’! for forced runs, followed by two numbers: the next timestamp at which we'll be allowed to run, and a measure of how much time it took to run this pass.

That information is mostly relevant while dpb is building lots of small packages very quickly.

Discrepancies between hosts that prevent them from starting up.
Size of work directory at the end of each build, built only with -s.
Simple log of the B=... line summaries. Mostly useful for making plots and tweaking performance.
Not a logfile at all, but a file created by the user to stop dpb creating new jobs.
Not a logfile at all, but created by the user to stop hostname creating new jobs.
Saves all terminal output, so that it can be replayed at hi speed with dpb-replay(1).
Logs the directories that were walked in the ports tree for dependency information, including the path to a dependency that triggered this particular step.

dpb performs best with lots of paths to build. When just used to build a few ports, there's a high risk of starvation as there are bottlenecks in parts of the tree.

Fetch jobs don't deal with checksum changes yet: if a fetch fails because of a wrong checksum, if you update the distinfo file and remove the lock, dpb won't pick it up.

Note that dpb does not manage installed packages in any intelligent way, it will just call pkg_add(1) during its depend stage to install its dependencies. With -u, it will call pkg_add -r. With -U, it will call pkg_add -r -D installed, but there is nothing else going on. This is especially true when using -R, ensure the machine is clean of possibly older packages first, or run dpb with -U.

In particular -R and -J together may lead to strange issues.

On heterogeneous networks, calibration of build info and choice of speed factors is not perfect, and somewhat a dark art. Using distinct speed factors on a build log that comes from a single machine works fine, but using the build info coming from several machines does not work all that well.

dpb should check /usr/include and /usr/X11R6/include for consistency, but it doesn't.

When a host fails consistency check, there is not yet a way to re-add it after fixing the problem. You have to stop dpb, cleanup and restart.

The default limits in login.conf are too small for bulk builds on any kind of parallel machines. Bump number of processes, file descriptors, and memory.

Even though dpb tries really hard to check heterogeneous networks for sanity (checking shared libraries and .la files), it is still dependent on the user to make sure all the hosts build ports the same way.

Make sure your NFS setup is consistent. The ports dir itself should be exported, including distfiles and packages repository, but the WRKOBJDIR should not be on NFS unless you have absolutely no choice, or if you exhibit deep masochistic tendencies. Pay particular attention to discrepancies in /etc/mk.conf.

Also, dpb connects to external hosts through ssh(1), relying on ssh_config(5) for any special cases.

dpb requires ssh protocol 2, and won't work with ssh 1. Currently, it doesn't even report a problem, it just won't start jobs.

When fetching distfiles, dpb may freeze and spin in a tight loop while the last distfiles are being fetched. This is definitely a bug, which has been around for quite some time, which is a bit difficult to reproduce, and hasn't been fixed yet. So if dpb stops updating its display right around the end of fetch, you've hit the bug. Just kill dpb and restart it.

clean-old-distfiles(1), dpb-replay(1), pkgpath(7)

Marc Espie

The original dpb command was written by Nikolay Sturm. This version is a complete rewrite from scratch using all the stuff we learnt over the years to make it better.

June 29, 2014 OpenBSD-5.7