..snip...
Local repository successfully rebuilt
Updating Synth repository catalogue...
Fetching meta.txz: 100% 260 B 0.3kB/s 00:01
Fetching packagesite.txz: 100% 54 KiB 54.9kB/s 00:01
Processing entries: 100%
Synth repository update completed. 207 packages processed.
Checking for upgrades (3 candidates): 100%
Processing candidates (3 candidates): 100%
Checking integrity... done (0 conflicting)
The following 2 package(s) will be affected (of 0 checked):
Installed packages to be UPGRADED:
synth: 0.98_2 -> 0.98_4
Installed packages to be REINSTALLED:
curl-7.46.0_2 (options changed)
The process will require 8 KiB more space.
[1/2] Upgrading synth from 0.98_2 to 0.98_4...
[1/2] Extracting synth-0.98_4: 100%
[2/2] Reinstalling curl-7.46.0_2...
[2/2] Extracting curl-7.46.0_2: 100%
Unfortunately, the system upgraded failed.
freebsd10 ~ %
if Unix.external_command (command)
if not Unix.external_command (command)
synth status ./PORTLIST
. Which brings me to my only nit, so far; make configure
the same way that the FreeBSD ports() framework does. Case in point; synth evaluated the list I fed it, and returned ~60 ports that it indicated I need to (re)configure -- make configure || rmconfig/configure. So I went through the list, and about half of those returned "configuration found for blah-blah-NN". So after finishing the list, I figured that synth would also mark those off the list. It didn't. So it appears to me, I will now have to memorize the options for each of those, prior to a rmconfig
followed by a configure
. A bit of a PITA, IMHO. Nothing I can't manage. Just wished I didn't have to. So after finishing the list, I figured that synth would also mark those off the list. It didn't.
make -C /usr/ports/<cat>/<port> rmconfig
and then synth status returns it as still bad, synth isn't looking at the same place as /usr/ports
is storing them.Thanks for the prompt reply, John.But it does. you can't even advance it if didn't. From the symptoms, I'd say you might have two locations for options, especially if you had a list of 60 obsolete cached options.
to iterate, if you "make -C /usr/ports/<cat>/<port> rmconfig" and then synth status returns it as still bad, synth isn't looking at the same place as /usr/ports is storing them.
synth status ./PORTLIST
returned a list of ~60 ports that the configure options were out of date, and hence; needed a make configure
. I went through them all, performing a make configure
about two thirds of them brought up the configuration dialog(). The other third returned Found configuration for port-blah-NN...
. My point is; if the configuration is considered up to date enough for the port itself. Then why doesn't synth agree (it still says I need to (re)configure the port)?Then why doesn't synth agree (it still says I need to (re)configure the port)?
The other third returned Found configuration for port-blah-NN....
make config
. build ./PORTLIST
now! #!/bin/sh -
# first create a list of all currently installed ports
pkg info >>./PORTLIST-RAW
#!/bin/sh -
# pkg(8) also prints a description of the ports listed
# we only want the port's names, get them
awk '{print $1;}' ./PORTLIST-RAW >./PORTLIST-CLEAN
#!/bin/sh -
# now all we need to do is prepend the category to
# those port names. I created the following script to
# accomplish just that
# create a categorized ports list to feed to
# ports-mgmt/synth
# place a list of port names, one per line *between*
# the following quotes
ports="
"
for name in $ports
do
pkg origin $name >>./PORTLIST-DO
# the following line is just to produce some status/feedback
echo $name
done
ports="
xterm-314
xtrans-1.3.5
zip-3.0_1
zziplib-0.13.62_2
"
Indeed it is.Oh well. It's the thought that counts, right?
OK in case anyone's interested. I cobbled up a script to build a complete list of ports installed on the system. So I could feed it to ports-mgmt/synth
synth rebuild-repository
or synth upgrade-system
?Thank you for the information, marino@I don't understand. Why don't you simply usesynth rebuild-repository
orsynth upgrade-system
?
Synth knows what you have installed, and it just builds those installed ports with those commands.
It seems to me that the whole script is unnecessary.
The task is complete. Final tally:
Initial queue size: 1024
packages built: 852
ignored: 1
skipped: 168
failed: 3
Duration: 14:27:24
The build logs can be found at: /var/log/synth
Would you like to rebuild the local repository (Y/N)? Y
Scanning entire ports tree.
progress: 98.05%
culprit: packages/All
Scan aborted for an unknown reason.
bad input for 'Value: ""
Failed to scan ports tree (Synth must exit)
FreeBSD dev-box 11.0-CURRENT FreeBSD 11.0-CURRENT #0 r294112:
Mon Jan 18 14:25:01 PST 2016 root@dev-box:/usr/obj/usr/src/sys/DEVBOX amd64
Path: /usr/src
Working Copy Root Path: /usr/src
URL: svn://svn.freebsd.org/base/head
Relative URL: ^/head
Repository Root: svn://svn.freebsd.org/base
Repository UUID: ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
Revision: 294112
Node Kind: directory
Schedule: normal
Last Changed Author: ak
Last Changed Rev: 294111
Last Changed Date: 2016-01-15 15:13:01 -0800 (Fri, 15 Jan 2016)
Path: /usr/ports
Working Copy Root Path: /usr/ports
URL: svn://svn.freebsd.org/ports/head
Relative URL: ^/head
Repository Root: svn://svn.freebsd.org/ports
Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5
Revision: 406193
Node Kind: directory
Schedule: normal
Last Changed Author: madpilot
Last Changed Rev: 406193
Last Changed Date: 2016-01-15 14:38:36 -0800 (Fri, 15 Jan 2016)
synth-0.98_2
Name : synth
Version : 0.98_2
Installed on : Wed Jan 20 07:43:43 2016 PST
Origin : ports-mgmt/synth
Architecture : freebsd:11:x86:64
Prefix : /usr/local
Categories : ports-mgmt
Licenses : ISCL
Maintainer : marino@FreeBSD.org
WWW : https://github.com/jrmarino/synth
Comment : Custom package repository builder for FreeBSD and DragonFly
Additional information, in case it helps:
Code:synth-0.98_2 Name : synth Version : 0.98_2
pkg upgrade synth
because portsmon says 0.98_4 is available everywhere synth build /BUILDLIST
. Before you remind me about rebuild-repository
, or upgrade-system
, I just want to know that It'll finish a task completely, and uneventfully, before I make a full commitment, and let alter my system. ELF interpreter /libexec/ld-elf.so.1 not found, error 2
Before you remind me about rebuild-repository, or upgrade-system, I just want to know that It'll finish a task completely, and uneventfully, before I make a full commitment, and let alter my system
synth build-repository
doesn't alter the system. It's just assembling information about all the build packages, but that's it.Why would you think that? It's Synth's job.I would have figured that pkg() would reconcile any dependencies.