sudo pkg delete -a
delete all files in: /var/synth/live_packages/All
cd /usr/ports/ports-mgmt/synth
sudo make install clean
sudo synth build /home/me/build.list
make, install, clean
. make -C /usr/ports/x11-servers/xorg-server config
to set the desirable options before starting the compilation. However, the instructions recommend to further disable sysutils/hal in all other ports that might have HAL option. This gave me a pause because I do not know how to ascertain that one of the dependencies does not have sysutils/hal option. The make, install, clean
interrupts the compilation at every dependency with options, so one could check. However, with mgmt-ports/synth it seems practically impossible to set the configuration for all the dependencies using the make -C /usr/ports/[category]/[portname] config
.OPTIONS_UNSET = HAL
OPTIONS_UNSET = CUPS HAL
synth prepare-system
afterwards to let Synth rebuild any changes.the items are not "obsolete".
They are likely build dependencies.
For example, "gmake". You need "gmake" to build a package, but you don't need it after that.
If you deleted "gmake" package, synth would have to build it again.
Synth deletes truly obsolete packages (older versions) when the repository is generated, so the actual repository is 100% current.
Bottom line: the packages you don't use are not worth worrying about. I'm surprised the number is so low. I would expect a lot more than 3 packages out of 152 to be "build-only".
pkg delete
all the packages off the server and reinstall them. That is an important step if your migrating from portupgrade/portmaster, otherwise you have all sorts of build dependencies installed on the system for no reason.cd /var/synth/live_packages/All
rm -rf *.txz
synth just-build `cat /home/build.list`
synth rebuild-repository
pkg delete -af
/usr/sbin/pkg bootstrap
pkg install `cat /home/build.list`
$ pkg stats
Local package database:
Installed packages: 103
Disk space occupied: 567 MiB
Remote package database(s):
Number of repositories: 1
Packages available: 142
Unique packages: 142
Total size of packages: 193 MiB
thread <something> exits with resources held!' at line 316 in file /usr/src/lib/libthr/thread/thr_exit.c (errno = 2)
#if defined(_PTHREADS_INVARIANTS)
if (THR_IN_CRITICAL(curthread))
PANIC("thread %p exits with resources held!", curthread);
#endif
...
#define THR_IN_CRITICAL(thrd) \
(((thrd)->locklevel > 0) || \
((thrd)->critical_count > 0))
Sooo.. any hints on what to do post python-flavors change 11/30/2017? Everything python related (and above) fails due to requiring "py27-setuptools>0:devel/py-setyptools@py27" which "does not exist".
Why are you recommending Poudriere in a Synth thread as a means of a fix?
support was planned, but introducing it 3 months early catches me by surprise.
On the plus side, at least I now how real ports to test it against.
Thank you for this and all the work you have been offering to BSD community. It is quite inspiring.new version released for flavors support, see Thread 63525
synth prepare-system
request, I get:Stand by, updating external repository catalogs ... done.
Scanning existing packages.
Scanning existing packages.
Queue integrity lost! (Synth must exit)
Unfortunately, the system upgrade failed.