| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
on the first in path. Fixes possible issues with Solaris.
|
|
the "cvs" command inside the su returns an error, that should be ignored.
(Aparently cvs returns "1" even if it's done a successful update but if
there were some files removed on purpose).
|
|
|
|
|
|
|
|
1) When checking if any of the required binary pkgs is newer, it's
not good to look into the (already existing) binary pkg, as that
might be unchanged. Instead, look at the DEPENDS.
In the context of the recent jpeg changes, the gd package itself was
not changed, but the DEPENDS were (via buildlink files). Now looking
into the existing gd binary pkg still said it wanted jpeg-6b instead
of the now-wanted jpeg>=6b, which was only available via the DEPENDS.
That's the first chunk of the patch below.
2) While debugging this, I found that the change in rev. 1.48 was
wrong, as can be seen throughout the last bulk build, search for errors
like:
find: "/usr/cvs.local/pkgsrc/packages/i386/All/gd-2.0.15.tgz": No such file or directory
As the whole operation is really on two files (as assured by "pkg_admin
lsbest" for pkg and REFS by definition), the quotes can be ommitted.
Why this wasn't caught when that change was tested is beyond me - maybe
different sh(1) behaviour? (The error happened on 1.6.1_STABLE, see
e.g. http://smaug.fh-regensburg.de/~feyrer/ftp/pub/NetBSD/pkgstat-i386/last/www/p5-Template-Toolkit/.broken.yui.html).
Anyways, that's addressed in the second part of the patch below, too.
3) Use ${FIND} while there.
|
|
files to preserve in sync with reality.
|
|
cd pkgsrc/mk
cvs update -Pd -A
cvs update -Pd -j pkgviews-mk-base -j pkgviews-mk
|
|
|
|
|
|
|
|
|
|
from pkgsrc current.
|
|
Observed from Gavan's Solaris bulk build.
|
|
hosting system.
|
|
from gavan@.
|
|
Introduce sandboxEmptyFiles a list of files to create empty in the
sandbox if they exist on the hosting system. Hence put /var/run in
sandboxEmptyDirs list.
Use $cppprog instead of cp.
|
|
|
|
in the sandbox if they exist on the hosting system: put /var/spool/mqueue
as it was already created before and add /var/log for now (needed
for various packages, like security/ssh2).
Only create /var/run/utmp(x) if they exist on the hosting system.
XXX this may better be an opsys dependent action.
|
|
causes problems with some awks. Patch provided by Jonathan Perkin in
PR pkg/22246
|
|
quote a shell test, and run ${AWK} -f tflat instead of using
#!/usr/bin/awk.
|
|
care not to blow away our bootstrap-pkgsrc stuff in the initial phase.
Also mark devel/bmake and devel/mk-files as broken on non-NetBSD so as not
to blow away our precious files from the bootstrap process in the middle
of a bulk-build. Now let's see if bulk-building works on Linux...
|
|
|
|
|
|
|
|
the bulk-install target to work.)
|
|
|
|
mksandbox. From Brook G. Milligan.
|
|
|
|
|
|
summary email list correctly the packages which are broken because of
their dependencies. Problem noted on Huberts most recent bulk build.
|
|
|
|
location. They are not really part of the bulk build stuff.
|
|
full pathname to the kernel file (e.g. for NetBSD /netbsd, OpenBSD /bsd, etc)
|
|
except for one peculiar thing: bmake does not pick up a definition for CC.
Something is missing (for SunOS).
|
|
Provided that I copy a working gcc and the binaries from the bootstrap kit
into the sandbox manually, this gets me as far as having a pkgsrc
sandbox that can build pkg_tools/pkg_install.
|
|
2. Introduce sandboxDirs, a list of directories that need to be
null mounted. This is different (e.g. on SunOS).
|
|
(et al.).
2. Use the loopback filesystem on Solaris.
|
|
|
|
|
|
can stop builds when a dependency is broken, yet continue builds
when a dependency is merely skipped (usually because it duplicates
functionality in the base system). Thus IGNORE_FAIL, the
oft-misunderstood and naught-documented option, goes away.
This addresses many people's complaints on tech-pkg@ and other
lists, as well as PR pkg/18157.
|
|
for localpatches and to make that directory available in the sandbox.
|
|
fails, then abort the build.
|
|
+ umount filesystems in the reverse order from that which they were mounted
+ null-mount /lib and /libexec in a way more consistent with the original
|
|
back to the current page, just list it as regular text.
- Put each dependency hyperlink on a separate line in the README.html file.
These were both noted by Thomas Klausner in a private email.
|
|
avoid simply appending to it.
- add some additional error checks when using the -r/--restart options to
make sure that the database exists and give a useful error message if it
doesn't
|
|
directory of a single package (e.g. graphics/gimp) for which a README.html
is to be generated. This provides the required hook to be able to use this
script to generate a README.html file for a single package as well as
for all packages.
|
