turns out my setup has links so that dpb -R is happy in chroot's...
and no ownership issue either.
Fix it so it works.
Also put the uptodate check earlier since that's internal.
Error: newgroup _thingsd: not registered in ports/infrastructure/db/user.list
Error: newuser _thingsd: not registered in ports/infrastructure/db/user.list
Fix UID/GID.
DBD::SQLite::st execute failed: NOT NULL constraint failed:
_Ports.PERMIT_DISTFILES at /usr/ports/databases/sqlports/files/Inserter.pm
line 196.
s/PERMIT_DISTILES/PERMIT_DISTFILES/
We won't be distributing CDROM anymore, so simplify to
just PERMIT_PACKAGE / PERMIT_DISTFILES
In particular, the new variables are shorter, so this makes
for better cosmetic sense in ports.
The "current" version allows for the old variables to die out
peacefully, at our leasure, and then I'll remove the old stubs.
As discussed with sthen@, various people agree, and deraadt@
is okay with the strategic change.
This does survive a bulk.
PLEASE NOTE: built packages require current pkg* tools.
In particular, the current version deals with
@comment pkgpath=* ftp=*
just fine, but the old one WILL COMPLAIN about missing cdrom info.
register-plist also doesn't care, adding/removing cdrom info
is a no-op for it. There is NO BUMP needed for the conversion.
For now, sqlports STILL carries the old variables. I'll deal
with their removal later.
Follow the upstream recommendations for packagers and switch to
multi-packages:
devel/gettext -> devel/gettext,-runtime
devel/gettext-tools -> devel/gettext,-tools
(new) devel/gettext,-textstyle
figuring things better doesn't work, and it seems to do exactly
what's required in each case.
do that for stuck jobs as well
fix a long standing oddity where stuck jobs wouldn't log but spew
error messages instead.
tweak the actual plist writer to do two passes:
first pass actually determines object names, and second pass
does the writing.
That way, the first pass can create "canonical" names where
${MODPY_PYCACHE} vanishes, and the second pass can sprinkle
@comment in front of the duplicate dirs.
okay afresh1@
When python ports move from python 2 + 3 to only a single version
or the other way we need to reset some values for that to take
effect.
go with it, cwen@
*.so.*, *.so, or *.a. Probably most likely to do this by mistake with p5-*
things if copying too much from an existing port, or some multipackages
cases. ok afresh1@ kn@
modify the PortBuilder -> Job::Port interface so that differences
are obvious.
tweak wipe to avoid wiping what we're currently actually running,
and also clean the "right" flavor in case we gave a wrong pkgpath name.