Re: Vim and Vim-lite ports broken options
On Sun, Jun 30, 2013 at 01:37:36AM +0200, Nikola Pavlović wrote: Hello, Is it just me, or did the last revision[*] of editors/vim break options for both it and editors/vim-lite? When I try to update vim-lite optional dependencies from vim are forced on this port, so I get mandatory Python, Lua, Ruby... with vim-lite. :) Yea, same here. I pinged obrien yesterday but no reply yet. -- Joel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ databases/jasperreports | 3.7.6 | 5.2.0 +-+ deskutils/taskjuggler | 3.4.0 | 3.5.0 +-+ www/xpi-pentadactyl | 20130407| 20130630 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portsc...@freebsd.org Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Vim and Vim-lite ports broken options
(Please keep me CC'd as I'm not subscribed to -ports)
Yup, it's all broken. I use vim-lite myself; the solution I found
is to drop this into /etc/make.conf:
.if ${.CURDIR:M*/editors/vim-lite}
WITH_VIM_OPTIONS=yes
.endif
Then cd /usr/ports/editors/vim-lite ; make config, make sure
everything is de-selected, and it should be fine from there; the only
dependencies at that point will be libiconv and libtool. This causes
the port to use the OPTIONS framework.
Do not ask me why this flag exists, as from what I can discern the
standard OPTIONS framework should suffice without sub-knobs. I get
the impression the driving force is to induce a non-interactive
behaviour, e.g. what BATCH sort of used to do (not sure if it still
does).
There seems to be an unspoken reluctance upon the part of a single
committer who also happens to maintain very key/important ports. A
similar situation happened with shells/bash, prompting shells/bash-devel
to be created/maintained by someone else. There are public discussions
about that, multiple times:
http://lists.freebsd.org/pipermail/freebsd-ports/2013-May/083948.html
http://lists.freebsd.org/pipermail/freebsd-ports/2013-January/080336.html
http://lists.freebsd.org/pipermail/freebsd-ports/2013-January/080363.html
http://lists.freebsd.org/pipermail/freebsd-ports/2013-January/080656.html
The key/major discussion I cannot find right now (maybe it wasn't on -ports,
that's all I looked at, and only for the word bash).
P.S. -- Unrelated to this matter, but the patch count for 7.3 is now up
to 1278 (i.e. the submitted patch count is up to 1278):
https://groups.google.com/forum/#!forum/vim_dev
Bram should be completely and totally ashamed (all while simultaneously
blabbing about too many patches, test 7.4 in May, yet there is no
such thing anywhere); a very sad state of affairs for such an important
editor.
--
| Jeremy Chadwick j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Making life hard for others since 1977. PGP 4BD6C0CB |
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Problem building ports in a sandbox/jail using DESTDIR
Hi. I am trying to compile ports in a sandbox environment on
FreeBSD-9.1-RELEASE using a snapshot of ports from 06/27/2013.
I have a jail file system I setup using my own scripts that I am pointing
$DESTDIR to. I am using 'zip' as the port for testing.
The problem is, I get an error like this and it immediately aborts.
cd: /tmp/mountpoint.TJizHb/data/freebsd/ports/ports-20130627/archivers/zip: No
such file or directory
Below is the output with DESTDIR debugging turned on.
# realpath .
/data/freebsd/ports/ports-20130627/archivers/zip
# make DESTDIR=/data/freebsd/ports/jail WITH_DESTDIR_DEBUG=1
=== Creating some important subdirectories
DEBUG: _DESTDIR_MOUNT_LIST= PORTSDIR:/usr/ports:___temp___
DISTDIR:/usr/ports/distfiles:___temp___
DEBUG: Processing PORTSDIR:/usr/ports:___temp___
DEBUG:
PORTSDIR:/data/freebsd/ports/ports-20130627:/data/freebsd/ports/jail/___temp___
DEBUG: Creating temporary mount point
DEBUG: Temporary mount point /data/freebsd/ports/jail/tmp/mountpoint.TJizHb
created successfully
DEBUG: Directory /data/freebsd/ports/ports-20130627 mounted
DEBUG: Processing DISTDIR:/usr/ports/distfiles:___temp___
DEBUG: DISTDIR:/data/freebsd/ports/distfiles:/data/freebsd/ports/jail/___temp___
DEBUG: Creating temporary mount point
DEBUG: Temporary mount point /data/freebsd/ports/jail/tmp/mountpoint.ZxFnzJ
created successfully
DEBUG: Directory /data/freebsd/ports/distfiles mounted
DEBUG: Handling devfs separately
DEBUG: devfs mounted
DEBUG: Things we mounted: /data/freebsd/ports/jail/dev
/data/freebsd/ports/jail/tmp/mountpoint.ZxFnzJ
/data/freebsd/ports/jail/tmp/mountpoint.TJizHb
DEBUG: Things we created: /data/freebsd/ports/jail/tmp/mountpoint.ZxFnzJ
/data/freebsd/ports/jail/tmp/mountpoint.TJizHb
DEBUG: _var_path_list: PORTSDIR=/tmp/mountpoint.TJizHb
DISTDIR=/tmp/mountpoint.ZxFnzJ DEVFS=/dev
=== Starting chrooted make in /data/freebsd/ports/jail...
cd: /tmp/mountpoint.TJizHb/data/freebsd/ports/ports-20130627/archivers/zip: No
such file or directory
=== Chrooted make in /data/freebsd/ports/jail failed
=== Cleaning up...
*** [do-chroot] Error code 2
Stop in /data/freebsd/ports/ports-20130627/archivers/zip.
Where it tries to cd to
/tmp/mountpoint.TJizHb/data/freebsd/ports/ports-20130627/archivers/zip
--
the underlined part should not be there. Ports is mounted directly on
/tmp/mountpoint.TJizHb in the jail by the makefiles and I verified that
/tmp/mountpoint.TJizHb/archivers/zip does exist at this point just prior to
getting the 'cd' error and cleaning up, by stopping the makefile there
and manually checking.
Makefile code in ports
==
Mk/bsd.destdir.mk
...
${ECHO_MSG} === Starting chrooted make in ${DESTDIR}...; \
export $${_var_path_list}; \
${CHROOT} $${_destdir} ${SH} -c \
cd $${PORTSDIR}${.CURDIR:S|^${PORTSDIR}||}; \
${SETENV} -i ${DESTDIR_ENV} $${_var_path_list} ${MAKE} ${.TARGETS} \
{ status=$$?; ${ECHO_MSG} === Chrooted make in ${DESTDIR}
succeeded; } || \
{ status=$$?; ${ECHO_MSG} === Chrooted make in ${DESTDIR} failed;
}; \
${ECHO_MSG} === Cleaning up...; \
...
The problem seems to be with
cd $${PORTSDIR}${.CURDIR:S|^${PORTSDIR}||};
I don't quite understand the expansion.
$PORTSDIR seems to be set to '/data/freebsd/ports/ports-20130627',
so I don't know how it is getting '/tmp/mountpoint.TJizHb' prepended, or why
the full path to the ports directory outside the jail is being used in this
expansion to cd to it inside the jail.
Could this be a bug in the ports makefile or is it possible that I am
missing something in my jail that can cause this?
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
CFT: [patch] making -jX builds the default
Hi there,
In attempt to catch (hopefully) last few remaining jobs-unsafe ports, and
thus to make upcoming expruns fallouts easier to handle, I'm sending small
patch I've been using locally for a while to get larger exposure. Patch
was sent to portmgr@ guys for review about a month earlier, it seems DTRT
at the first glances. :-)
FORCE_MAKE_JOBS is removed because it is the default. While here, I've
moved empty(MAKE_JOBS_NUMBER) check higher, IMHO where it should belong,
also saves a few lines. Testing and feedback are welcome! Let's finally
flip the damn switch! ;-)
./danfe
Index: bsd.port.mk
===
--- bsd.port.mk (revision 322093)
+++ bsd.port.mk (working copy)
@@ -912,9 +912,6 @@
#To be used with known bad ports.
# DISABLE_MAKE_JOBS
# - Set to disable the multiple jobs feature.
User settable.
-# FORCE_MAKE_JOBS
-# - Force all ports to be built with multiple
jobs, except ports
-#that are explicitly marked MAKE_JOBS_UNSAFE.
User settable.
# MAKE_JOBS_NUMBER
# - Override the number of make jobs to be used.
User settable.
## cacche
@@ -2167,20 +2164,15 @@
# Multiple make jobs support
.if defined(DISABLE_MAKE_JOBS) || defined(MAKE_JOBS_UNSAFE)
_MAKE_JOBS=#
+MAKE_JOBS_NUMBER?= 1
.else
-.if defined(MAKE_JOBS_SAFE) || defined(FORCE_MAKE_JOBS)
MAKE_JOBS_NUMBER?= `${SYSCTL} -n kern.smp.cpus`
_MAKE_JOBS?= -j${MAKE_JOBS_NUMBER}
-.if defined(FORCE_MAKE_JOBS) !defined(MAKE_JOBS_SAFE)
-BUILD_FAIL_MESSAGE+= You have chosen to use multiple make jobs
(parallelization) for all ports. This port was not tested for this setting.
Please remove FORCE_MAKE_JOBS and retry the build before reporting the failure
to the maintainer.
+.if !defined(MAKE_JOBS_SAFE)
+BUILD_FAIL_MESSAGE+= Try to set MAKE_JOBS_UNSAFE=yes and rebuild before
reporting the failure to the maintainer.
.endif
.endif
-.endif
-.if empty(MAKE_JOBS_NUMBER)
-MAKE_JOBS_NUMBER= 1
-.endif
-
# ccache support
# Support NO_CCACHE for common setups, require WITH_CCACHE_BUILD, and
# don't use if ccache already set in CC
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: CFT: [patch] making -jX builds the default
On 06/30/13 16:40, Alexey Dokuchaev wrote: Hi there, In attempt to catch (hopefully) last few remaining jobs-unsafe ports, and thus to make upcoming expruns fallouts easier to handle, I'm sending small patch I've been using locally for a while to get larger exposure. Patch was sent to portmgr@ guys for review about a month earlier, it seems DTRT at the first glances. :-) FORCE_MAKE_JOBS is removed because it is the default. While here, I've moved empty(MAKE_JOBS_NUMBER) check higher, IMHO where it should belong, also saves a few lines. Testing and feedback are welcome! Let's finally flip the damn switch! ;-) +1 I've been running with FORCE_MAKE_JOBS for a long time and rarely encounter issues. Steve ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Subversion 1.8 / FreeBSD 8 x86 STABLE Symlinks
When using svn 1.8 I have come across a situation where when it is used pointing to a symlink that refers to a working directory that a update will either segfault or exit prematurely and leave a lock held on the working directory that the symlink points to. This leaves you with one choice but to run cleanup on the referenced actual working directory which was AFAIK never the case for any version below 1.8. Not sure if this is a problem with svn or FreeBSD itself but thought I would report the characteristics in case it's noticed elsewhere. Details: Using UFS FreeBSD 8-STABLE i386 as of this date. In the directory... cd /exports/usr ln -s src8 src svn up /exports/usr/src -- Jason Hellenthal Inbox: jhellent...@dataix.net Voice: +1 (616) 953-0176 JJH48-ARIN smime.p7s Description: S/MIME cryptographic signature
Re: Subversion 1.8 / FreeBSD 8 x86 STABLE Symlinks
On Sun, Jun 30, 2013 at 02:20:21PM -0400, Jason Hellenthal wrote: When using svn 1.8 I have come across a situation where when it is used pointing to a symlink that refers to a working directory that a update will either segfault or exit prematurely and leave a lock held on the working directory that the symlink points to. This leaves you with one choice but to run cleanup on the referenced actual working directory which was AFAIK never the case for any version below 1.8. Not sure if this is a problem with svn or FreeBSD itself but thought I would report the characteristics in case it's noticed elsewhere. Details: Using UFS FreeBSD 8-STABLE i386 as of this date. In the directory... cd /exports/usr ln -s src8 src svn up /exports/usr/src Known bug/problem in Subversion, not FreeBSD: http://svn.apache.org/viewvc?view=revisionrevision=r1496007 Previous discussion: http://lists.freebsd.org/pipermail/freebsd-questions/2013-June/251842.html -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Making life hard for others since 1977. PGP 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Problem building ports in a sandbox/jail using DESTDIR
On Sun, Jun 30, 2013 at 11:29:53AM -0500, Vincent Stemen wrote:
Hi. I am trying to compile ports in a sandbox environment on
FreeBSD-9.1-RELEASE using a snapshot of ports from 06/27/2013.
I have a jail file system I setup using my own scripts that I am pointing
$DESTDIR to. I am using 'zip' as the port for testing.
The problem is, I get an error like this and it immediately aborts.
cd: /tmp/mountpoint.TJizHb/data/freebsd/ports/ports-20130627/archivers/zip:
No such file or directory
Disregard. I resolved it.
I figured out what the variable expansion is doing for the 'cd' command.
The problem was due to the fact that my /usr/ports is a sym-link to
/data/freebsd/ports/ports-20130627 so ${.CURDIR} didn't coincide with
the default setting of '/usr/ports' for $PORTSDIR, so the substitution,
$${PORTSDIR}${.CURDIR:S|^${PORTSDIR}||}, returned the wrong path.
I just had to set $PORTSDIR to the full real path of the ports
directory.
It would be a nice enhancement to the make file though, to handle
/usr/ports being a sym-link without having to set $PORTSDIR to the full
real path :-).
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
please take ports/179236
Would anyone mind taking ports/179236? ports/179236: Build failure (lib-depends) for net/tigervnc when HPJPG is enabled http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/179236 Thanks, -- `whois vmeta.jp | nkf -w` meta m...@vmeta.jp ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
