AUDITFILE default for ports users
Hi,
I have some machines on which, for various reasons, only ports are used.
On upgrading ports, I keep running into the the fact that
/var/db/pkg/vuln.xml is lagging behind /usr/ports/security/vuxml/vuln.xml
which is updated via portsnap (and thus upgrading the vulnerable ports
fails).
So I'd like to propose defaulting to vuln.xml from ports if it is newer
that the one from /var/db/pkg/ and AUDITFILE is not defined by the user.
Tentative patch attached (I'm not happy with the != constuct).
--
IOnut - Un^d^dregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID 29597D20
Index: bsd.port.mk
===
--- bsd.port.mk (revision 392405)
+++ bsd.port.mk (working copy)
@@ -2970,14 +2970,15 @@
# Check if the port is listed in the vulnerability database
-AUDITFILE?= ${PKG_DBDIR}/vuln.xml
-_EXTRACT_AUDITFILE= ${CAT} ${AUDITFILE}
+_AUDITFILE!= ${TEST} ${PORTSDIR}/security/vuxml/vuln.xml -nt ${PKG_DBDIR}/vuln.xml \
+ ${ECHO} ${PORTSDIR}/security/vuxml/vuln.xml || ${ECHO} ${PKG_DBDIR}/vuln.xml
+AUDITFILE?= ${_AUDITFILE}
check-vulnerable:
.if !defined(DISABLE_VULNERABILITIES) !defined(PACKAGE_BUILDING)
@if [ -f ${AUDITFILE} ]; then \
if [ -x ${PKG_BIN} ]; then \
- vlist=`${PKG_BIN} audit ${PKGNAME} || :`; \
+ vlist=`${PKG_BIN} audit -f ${AUDITFILE} ${PKGNAME} || :`; \
if [ $${vlist} = 0 problem(s) in the installed packages found. ]; then \
vlist=; \
fi; \
___
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: AUDITFILE default for ports users
On Sat, 18 Jul 2015 17:30:52 -0500 Mark Felder f...@feld.me wrote: On Jul 18, 2015, at 06:17, Ion-Mihai Tetcu ite...@freebsd.org wrote: Hi, I have some machines on which, for various reasons, only ports are used. On upgrading ports, I keep running into the the fact that /var/db/pkg/vuln.xml is lagging behind /usr/ports/security/vuxml/vuln.xml which is updated via portsnap (and thus upgrading the vulnerable ports fails). So I'd like to propose defaulting to vuln.xml from ports if it is newer that the one from /var/db/pkg/ and AUDITFILE is not defined by the user. Tentative patch attached (I'm not happy with the != constuct). I might be slightly lost here regarding what issue you're hitting. Described above :) I'm mostly an old-time ports user (as opposed to packages user). The vuln.xml database at /var/db/pkg/vuln.xml is updated by /usr/local/etc/periodic/security/410.pkg-audit on a nightly basis. Yes, and if a fix for an know vuln was just committed, updating the ports tree and upgrading the port will get the system patched faster that waiting for the package to be built on the cluster. A ports user would portsnap the ports, which will get a more up-to-date vuln.xml that the one that was fetched by nightly cron. If your database is out of date you can simply force a fetch of the database with `pkg audit -F`. Yes, or define AUDITFILE to be the one from ports in make.conf. However both require manual action; I'm just proposing a (I think sane) default. Sometimes I leave /usr/ports/security/vuxml/vuln.xml in an unfinished state from working on creating new entries One could argue you should do devel on an svn co'ed copy of the tree, not the system one :) so I don't regard this as an valid argument. and I am not sure I would want the ports tree to think it should use that database just because it has a newer timestamp. I don't know a cheaper way to check if it's more up-to-date. I suppose I would have to think about this a bit more... I'm not sure. Having two sources of truth seems like a disaster waiting to happen. True. But except if http://vuxml.freebsd.org/freebsd/vuln.xml.bz2 update is triggered by each commit it will lag behind the (master) version in the ports tree. How often is updated this file fetched by `pkg audit -F`? At lest for now, one can't really mix ports and packages on a daily bases; a ports user would tend to ignore pkg features not directly related to locally installed package management (delete/which/info/...). I'm curious to hear what the other ports-secteam members think. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 29597D20 ___ 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: Share your pkg aliases
On Thu, 2 Apr 2015 22:19:10 +0200 Baptiste Daroussin b...@freebsd.org wrote: Hi, For pkg 1.5.0 we do plan to provide a default pkg.conf full of useful aliases, of course this is subjective, if you think you have added some useful aliases into your pkg.conf please share those so we can add them directly into the next release. options: query -i %n - %Ok: %Ov, roptions: rquery -i %n - %Ok: %Ov, comment: query -i %c, desc: query -i %e, roptions is particularly useful to see if the default options fit one's needs (either on the initial install or on an upgrade when OPTIONS changed). -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 29597D20 ___ 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: FreeBSD apcupsd port - patch for APC 9606 SNMP cards
I have no problem integrating this patch, but it should be really submitted upstream ... On Tue, 19 Feb 2013 09:16:37 -0800 birch bi...@naturalpoint.com wrote: Hello again, Just did an upgrade to FreeBSD 9.1 and I noticed that the apcupsd port still has this crash and requires the patch. It would be fantastic if the patch below could be integrated into the port for those of us who are using 9606 SNMP cards. Also adding a CC to po...@freebsd.org in case the email address for the port maintainer is not being checked. Many thanks! birch --- sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/snmplite/apc-mib.cpp +++ sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/snmplite/apc-mib.cpp @@ -307,6 +307,8 @@ break; case CI_Overload: + if (data.str.len() 9) + break; Dmsg1(80, Got CI_Overload: %c\n, data.str[8]); if (data.str[8] == '1') ups-set_overload(); birch wrote on 7/19/2012 10:33 AM: Hello, The current version of apcupsd in the ports tree for FreeBSD 8.3 no longer works with APC ups's connected via APC 9606 SNMP cards. Would it be possible to get the following patch added to the port, and/or passed upstream? The link below describes the problem and fix in more detail, I have included their patch in this email. I have verified that this patch fixes resolves the issue on FreeBSD 8.3 and allows apcupsd to run without crashing on startup. Thank you, birch Debian Bug report logs - #655741 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655741 Here is the patch as I tested it : --- sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/snmplite/apc-mib.cpp +++ sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/snmplite/apc-mib.cpp @@ -307,6 +307,8 @@ break; case CI_Overload: + if (data.str.len() 9) + break; Dmsg1(80, Got CI_Overload: %c\n, data.str[8]); if (data.str[8] == '1') ups-set_overload(); -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID F0808380 ___ 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
llvm-3.2 tarball rerolled?
Hi, I'm seeing this size mismatch, any idea what it is about? root(itetcu)@it/SU -SSH- /usr/ports/devel/llvm [23:50:47] 0 # make === Found saved configuration for llvm-3.1 = llvm-3.2.src.tar.gz doesn't seem to exist in /usr/ports/distfiles/. = Attempting to fetch http://llvm.org/releases/3.2/llvm-3.2.src.tar.gz fetch: http://llvm.org/releases/3.2/llvm-3.2.src.tar.gz: size mismatch: expected 12275252, actual 12275082 = Attempting to fetch ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/llvm-3.2.src.tar.gz fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/llvm-3.2.src.tar.gz: File unavailable (e.g., file not found, no access) = Couldn't fetch it - please try to retrieve this Tnx, -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID F0808380 ___ 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: sshguard dumping core on 9-STABLE
On Wed, 2 Jan 2013 20:27:46 +0200
Konstantin Belousov kostik...@gmail.com wrote:
On Wed, Jan 02, 2013 at 02:38:34PM +0200, Ion-Mihai Tetcu wrote:
Hi,
I'm seeing shhguard-ipfw sig 10 on start on my machines updated to
9-STABLE (eg. FreeBSD 9.1-STABLE #5 r244924: Tue Jan 1 19:45:55
EET 2013 :/usr/obj/usr/src/sys/GENERIC amd64 ) while on some
-PRERELEASE it's running fine. Anyone seeing something similar?
Recompile libc with the debugging and get the backtrace again.
Hm, here it is:
Core was generated by `sshguard'.
Program terminated with signal 10, Bus error.
Reading symbols from /lib/libthr.so.3...done.
Loaded symbols for /lib/libthr.so.3
Reading symbols from /lib/libc.so.7...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0 getenv (name=0x800b9267b TZ) at /usr/src/lib/libc/stdlib/getenv.c:438
438 if (environ == NULL || environ[0] == NULL)
[New Thread 801007800 (LWP 100516/sshguard)]
[New Thread 801007400 (LWP 100507/sshguard)]
(gdb) bt full
#0 getenv (name=0x800b9267b TZ) at /usr/src/lib/libc/stdlib/getenv.c:438
envNdx = value optimized out
#1 0x000800b61e11 in tzset_basic (rdlocked=1) at
/usr/src/lib/libc/../../contrib/tzcode/stdtime/localtime.c:1274
name = value optimized out
#2 0x000800b62112 in localtime_r (timep=0x7fffc138,
tmp=0x7fffc080) at
/usr/src/lib/libc/../../contrib/tzcode/stdtime/localtime.c:1483
No locals.
#3 0x000800b62270 in ctime_r (timep=value optimized out,
buf=0x7fffcd80 PÍÿÿÿ\177) at
/usr/src/lib/libc/../../contrib/tzcode/stdtime/localtime.c:1766
mytm = {tm_sec = -16072, tm_min = 32767, tm_hour = -12928, tm_mday =
32767, tm_mon = 0, tm_year = 0, tm_wday = 0, tm_yday = 0, tm_isdst = 4,
tm_gmtoff = 514,
tm_zone = 0x50e565d3 Address 0x50e565d3 out of bounds}
#4 0x000800b5d938 in vsyslog (pri=37, fmt=0x43e191 %s,
ap=0x7fffcdf0) at /usr/src/lib/libc/gen/syslog.c:178
cnt = value optimized out
ch = value optimized out
p = value optimized out
now = 1357211091
fd = value optimized out
saved_errno = 2
stdp = value optimized out
tbuf =
Ð\006\000\001\b\000\000\000{Wd\000\b\000\000\000\000\000\000\000\006\000\006\000ô¶\205\000\b\000\000\000
Âÿÿÿ\177\000\000\000´e\000\b\000\000\Âÿÿÿ\177\000\000ÐÁÿÿÿ\177\000\000\000\000\000\000\000\000\000\000¹zd\000\b,
'\0' repeats 35 times,
p\030\000\001\b\000\000\000\000\000\000\000p\030\000\001\b\000\000\000\b\000\000\000\200\v\000\001\b\000\000\000\000\000\000\000À\004\000\001\b\000\000\000\b\000\000\000À\004\000\001\b\000\000\000\000¸e\000\b\000\000\000(\006\000\001\b\000\000\000\001\000\000\000ÿ\177\000\000
\v\000\001\b\000\000\000\001\000\000\000\000\000\000\000@...
fmt_cpy =
¶Ëÿÿÿ\177\000\000óÌÿÿÿ\177\000\000ðÌÿÿÿ\177\000\000°Ëÿÿÿ\177\000\000ðÌÿÿÿ\177\000\000ÐÌÿÿÿ\177\000\000
Ëÿÿÿ\177\000\000\020Êÿÿÿ\177\000\000
®@\000\000\000\000\000`\214Û\000\b\000\000\000PÍÿÿÿ\177\000\000{Wd\000\000\000\000\000É®@\000\000\000\000\000íÌÿÿÿ\177\000\000pÊÿÿB\000\000\000{Wd\000\b\000\000\000\234ñ¸\000\002\000\002\000,l¨\000\b\000\000\000\220Êÿÿÿ\177\000\000\000¸e\000\b\000\000\000
Êÿÿÿ\177\000\000@Êÿÿÿ\177\000\000\000\000\000\000\000\000\000\000¹zd\000\b,
'\0' repeats 11 times, (...
timbuf =
PÍÿÿÿ\177\000\000\004\000\000\000\000\000\000\000íÌÿÿÿ\177\000\000ã\001
errstr = 1\017@\000\000\000\000\000W£°\a, '\0' repeats 13 times,
¸e\000\b\000\000\000`ú\001\001\b\000\000\000 ®@, '\0' repeats 13 times, ½
d\000\b\000\000
fp = (FILE *) 0x800dd3460
fmt_fp = value optimized out
tbuf_cookie = {base = 0x7fffc140 Ð\006, left = 2048}
fmt_cookie = {base = 0x8010011e0 @?d, left = 1}
#5 0x000800b5d838 in syslog (pri=value optimized out, fmt=value
optimized out) at /usr/src/lib/libc/gen/syslog.c:128
ap = {{gp_offset = 16, fp_offset = 48, overflow_arg_area =
0x7fffced0, reg_save_area = 0x7fffce10}}
#6 0x00403c6f in sshguard_log (prio=5, fmt=0x40aea0 Started
successfully [(a,p,s)=(%u, %u, %u)], now ready to scan.) at sshguard_log.c:129
ap = {{gp_offset = 40, fp_offset = 48, overflow_arg_area =
0x7fffcfd0, reg_save_area = 0x7fffcef0}}
__func__ = sshguard_log
#7 0x00402516 in main (argc=16906848, argv=0x80101d080) at
sshguard.c:222
tid = 0x801007800
retv = 942421043
source_id = 32767
buf = '\0' repeats 72 times,
{Wd\000\b\000\000\000\000\000\000\000\002\000\002\000\br¨\000\b\000\000\000
Ñÿÿÿ\177\000\000\000¸e\000\b\000\000\Ñÿÿÿ\177\000\000ÐÐÿÿÿ\177\000\000\000\000\000\000\000\000\000\000¹zd\000\b,
'\0' repeats 21 times, d\000\b, '\0' repeats 29 times,
d\000\b\000\000\000\030\203\205\000\b\00---Type return to continue, or q
return to quit---
0\000\0008u©\000\b, '\0' repeats 43 times,
\221e\000\b\000\000\000°Ñÿÿÿ\177\000\000\220Òÿÿÿ\177\000\000
sshguard dumping core on 9-STABLE
Hi,
I'm seeing shhguard-ipfw sig 10 on start on my machines updated to 9-STABLE
(eg.
FreeBSD 9.1-STABLE #5 r244924: Tue Jan 1 19:45:55 EET 2013
:/usr/obj/usr/src/sys/GENERIC amd64
) while on some -PRERELEASE it's running fine.
Anyone seeing something similar?
#0 0x000800b7dced in getenv () from /lib/libc.so.7
[New Thread 801007800 (LWP 100290/sshguard)]
[New Thread 801007400 (LWP 100146/sshguard)]
(gdb) bt full
#0 0x000800b7dced in getenv () from /lib/libc.so.7
No symbol table info available.
#1 0x000800b61e11 in tzsetwall () from /lib/libc.so.7
No symbol table info available.
#2 0x000800b62112 in localtime_r () from /lib/libc.so.7
No symbol table info available.
#3 0x000800b62270 in ctime_r () from /lib/libc.so.7
No symbol table info available.
#4 0x000800b5d938 in vsyslog () from /lib/libc.so.7
No symbol table info available.
#5 0x000800b5d838 in syslog () from /lib/libc.so.7
No symbol table info available.
#6 0x00403c6f in sshguard_log (prio=5, fmt=0x40aea0 Started
successfully [(a,p,s)=(%u, %u, %u)], now ready to scan.) at sshguard_log.c:129
ap = {{gp_offset = 40, fp_offset = 48, overflow_arg_area =
0x7fffd030, reg_save_area = 0x7fffcf50}}
__func__ = sshguard_log
#7 0x00402516 in main (argc=16907520, argv=0x80101d080) at
sshguard.c:222
tid = 0x801007800
retv = 775238193
source_id = 32767
buf = '\0' repeats 72 times,
{Wd\000\b\000\000\000\000\000\000\000\002\000\002\000\br¨\000\b\000\000\000\200Ñÿÿÿ\177\000\000\000¸e\000\b\000\000\000\220Ñÿÿÿ\177\000\Ñÿÿÿ\177\000\000\000\000\000\000\000\000\000\000¹zd\000\b,
'\0' repeats 21 times, d\000\b, '\0' repeats 29 times,
d\000\b\000\000\000\030\203\205\000\b\000\000\0008u©\000\b, '\0' repeats 44
times,
\221e\000\b\000\000\000\020Òÿÿÿ\177\000\000ðÒÿÿÿ\177\000\000\000\000\000\000\000\000\000\000ðÒÿÿÿ\177\000\000W{d\000\b\000\000\000Ã\020@\000\000\000\000\000\004Ï\212\006\000\000\000\000ôò\217ò\000\000...
Thanks,
--
IOnut
___
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: Nut-2.6.5 package failure due to non-existent entry in pkg-plist.
On Thu, 6 Dec 2012 22:29:20 +1100 Dewayne dewayne.gerag...@heuristicsystems.com.au wrote: Hi itetcu, Thank-you for maintaining this port, however on 9.1Release the package isn't being built. Would you please review the pkg-plist for /usr/ports/sysutils/nut. The file libexec/nut/newmge-shut isn't being created, or should be removed from pkg-plist as the entry is preventing nut from creating a package. Should be somewhat fixed now, thanks for reporting. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID F0808380 ___ 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: web FreeBSD Ports Search is out of sync
On Sun, 2 Dec 2012 08:50:18 +0200
Kimmo Paasiala kpaas...@gmail.com wrote:
On Sun, Dec 2, 2012 at 8:36 AM, Kevin Oberman kob6...@gmail.com
wrote:
On Sat, Dec 1, 2012 at 7:32 PM, Eitan Adler li...@eitanadler.com
wrote:
On 1 December 2012 11:46, Miroslav Lachman 000.f...@quip.cz
wrote:
Hi,
I don't know the details about infrastructure, but I found out
that web is showing lighttpd-1.4.31_5 [1] and svn ports tree has
1.4.32 for a 10 days [2]
Is it aftermath of the intrusion to the FreeBSD.org cluster?
I'll bet it has to do with the INDEX file which is not currently
being regenerated. I might be wrong though.
make -C /usr/ports make index should take care of it, though I'm
not positive. Building the INDEX can take between 5 and ??? minutes,
depending on the speed of your system.
It takes about half an hour on my dog slow intel atom D510. Is there
anything in the works to speed up 'make index'? I understand that the
slowest part is the evaluation of dependencies, is that right?
You might want to try ports-mgmt/p5-FreeBSD-Portindex
cache-init(1) will take that half an hour, but after that updating the
INDEX will take a minute or so (depending on what has changed in the PT
since your last update). Also you'll have an INDEX that reflects your
local settings (make.conf, OPTIONS).
# m /root/bin/ports_upd.sh
#!/bin/sh
DATE=`date +%Y-%m-%d_%H_%M_%S`
LOG_DIR=/var/log/ports
PSNAP_LOG=${LOG_DIR}/psnap.${DATE}
/usr/sbin/portsnap fetch
/usr/sbin/portsnap update | tee ${PSNAP_LOG}
/usr/local/bin/cache-update -f plain,options -i ${PSNAP_LOG} | tee
${PSNAP_LOG}.cu
grep -qv 'Nothing to do' ${PSNAP_LOG}.cu \
/usr/local/bin/portindex -v -o ${PORTSDIR}/INDEX-9
portmaster -L --no-index-fetch --index | egrep -B1 '(ew|ort)
version|Aborting|installed|dependencies|IGNORE|marked|Reason:|MOVED' | grep -v
'^--'
--
IOnut - Un^d^dregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID F0808380
___
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: web FreeBSD Ports Search is out of sync
On Sun, 02 Dec 2012 08:12:45 + Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 02/12/2012 06:50, Kimmo Paasiala wrote: It takes about half an hour on my dog slow intel atom D510. Is there anything in the works to speed up 'make index'? I understand that the slowest part is the evaluation of dependencies, is that right? The slow part is parsing around 25,000 Makefiles ( + reading about 25000 pkg-descr files, but that's relatively quick) in order to extract the values of certain variables. make(1) typically takes about 200ms per Makefile, which is ages. Speedups are possible: parallelization (which is what make index does) or cacheing the results and only rerunning make when changes could affect the output (which is what FreeBSD::Portindex does) Once you've done all that Makefile processing, chasing all the dependencies is fairly quick. A great deal of time and effort has been spent on making 'make index' run as fast as possible. All the easy optimizations and many of the not-so-easy ones have already been applied. Further improvement would probably require a radical 'throw it away and write something better from scratch' approach, which I'm not at all sure is worth it since for the most part, the ports works just fine without any sort of index at all, and it is the various websites that essentially show nicely formatted data from the INDEX that would really benefit. BTW, I'm seeing this on my machines: Checking timestamps on options makefiles: cache-update: WARNING unknown options file /var/db/ports/rsync/options -- ignored cache-update: WARNING unknown options file /var/db/ports/subversion/options -- ignored cache-update: WARNING unknown options file /var/db/ports/apr/options -- ignored cache-update: WARNING unknown options file /var/db/ports/python27/options -- ignored cache-update: WARNING unknown options file /var/db/ports/m4/options -- ignored cache-update: WARNING unknown options file /var/db/ports/help2man/options -- ignored cache-update:1: Checking for category changes at www # cat /var/db/ports/rsync/options # This file is auto-generated by 'make config'. # Options for rsync-3.0.9_2 _OPTIONS_READ=rsync-3.0.9_2 _FILE_COMPLETE_OPTIONS_LIST=ACL ATIMES FLAGS ICONV POPT_PORT RENAMED SSH TIMELIMIT OPTIONS_FILE_UNSET+=ACL OPTIONS_FILE_UNSET+=ATIMES OPTIONS_FILE_UNSET+=FLAGS OPTIONS_FILE_UNSET+=ICONV OPTIONS_FILE_UNSET+=POPT_PORT OPTIONS_FILE_SET+=RENAMED OPTIONS_FILE_SET+=SSH OPTIONS_FILE_UNSET+=TIMELIMIT Any hints? Is it the fact that it's in the OPTIONSng format? Thanks, -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID F0808380 ___ 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: web FreeBSD Ports Search is out of sync
On Sun, 02 Dec 2012 08:49:51 +
Matthew Seaman m.sea...@infracaninophile.co.uk wrote:
On 02/12/2012 08:22, Ion-Mihai Tetcu wrote:
You might want to try ports-mgmt/p5-FreeBSD-Portindex
cache-init(1) will take that half an hour, but after that updating
the INDEX will take a minute or so (depending on what has changed
in the PT since your last update). Also you'll have an INDEX that
reflects your local settings (make.conf, OPTIONS).
Thanks for the recommendation. Always glad to hear that people a
making use of my code.
I'm a fan since I was running it on an k6-II :)
# m /root/bin/ports_upd.sh
#!/bin/sh
DATE=`date +%Y-%m-%d_%H_%M_%S`
LOG_DIR=/var/log/ports
PSNAP_LOG=${LOG_DIR}/psnap.${DATE}
/usr/sbin/portsnap fetch
/usr/sbin/portsnap update | tee ${PSNAP_LOG}
/usr/local/bin/cache-update -f plain,options -i ${PSNAP_LOG} | tee
${PSNAP_LOG}.cu
Actually, nowadays you don't need to save the output of portsnap or
cvsup or whatever, and use '-f plain,options' to parse that. The
changes in version 2.8 mean portindex can detect when the timestamp
on any ports Makefile or pkg-descr file or the options saved
in /var/db/ports has changed, and determine what ports it needs to
recheck from that, so it's completely independent of the mechanism[*]
used to update the tree. This doesn't really take significantly more
or less time than the old 'parse the logfile' approach -- all those
make invocations are the slow step.
Just run 'cache-update' without arguments.
This depends on the speed of your disks and on many of my mahcines,
that is the limitting factor. On my home raidz that timestamp checking
made everyting a few times longer.
Besides, I like to have things logged.
grep -qv 'Nothing to do' ${PSNAP_LOG}.cu \
/usr/local/bin/portindex -v -o ${PORTSDIR}/INDEX-9
portmaster -L --no-index-fetch --index | egrep -B1 '(ew|ort)
version|Aborting|installed|dependencies|IGNORE|marked|Reason:|MOVED'
| grep -v '^--'
Cheers,
Matthew
[*] And less error prone.
As long as you use portsnap (ie. local port changes are discarded) and
you run cache-update each time, I don't see the difference.
--
IOnut - Un^d^dregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID F0808380
___
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: web FreeBSD Ports Search is out of sync
On Sun, 02 Dec 2012 09:16:20 + Matthew Seaman m.sea...@infracaninophile.co.uk wrote: On 02/12/2012 08:26, Ion-Mihai Tetcu wrote: BTW, I'm seeing this on my machines: Checking timestamps on options makefiles: cache-update: WARNING unknown options file /var/db/ports/rsync/options -- ignored cache-update: WARNING unknown options file /var/db/ports/subversion/options -- ignored cache-update: WARNING unknown options file /var/db/ports/apr/options -- ignored cache-update: WARNING unknown options file /var/db/ports/python27/options -- ignored cache-update: WARNING unknown options file /var/db/ports/m4/options -- ignored cache-update: WARNING unknown options file /var/db/ports/help2man/options -- ignored cache-update:1: Checking for category changes at www This should be harmless and should only report leftovers from removed ports or ports that have changed where they keep their options data. However rsync, subversion, m4, help2man at least are all very much live ports. Not sure exactly what is happening there. Yep, it's not the case. I installed this particular machine only this week. I suggest re-running cache-init and see if the problem goes away. Doing this now (but I think I did it on a different box w/o result). # cat /var/db/ports/rsync/options # This file is auto-generated by 'make config'. # Options for rsync-3.0.9_2 _OPTIONS_READ=rsync-3.0.9_2 _FILE_COMPLETE_OPTIONS_LIST=ACL ATIMES FLAGS ICONV POPT_PORT RENAMED SSH TIMELIMIT OPTIONS_FILE_UNSET+=ACL OPTIONS_FILE_UNSET+=ATIMES OPTIONS_FILE_UNSET+=FLAGS OPTIONS_FILE_UNSET+=ICONV OPTIONS_FILE_UNSET+=POPT_PORT OPTIONS_FILE_SET+=RENAMED OPTIONS_FILE_SET+=SSH OPTIONS_FILE_UNSET+=TIMELIMIT Any hints? Is it the fact that it's in the OPTIONSng format? If you're running 2.9 OPTIONSng should be handled correctly. It doesn't matter much: the exact format of the OPTIONS variables doesn't make much difference to building the INDEX, only detecting when they've been changed. # pkg info p5-FreeBSD-Portindex p5-FreeBSD-Portindex-2.9 Incremental FreeBSD ports INDEX file generation So what exactly are you checking WRT option files? -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID F0808380 ___ 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: opera 12.11 libpng error
On Wed, 28 Nov 2012 21:28:30 +0100 Ronald Klop ronald-freeb...@klop.yi.org wrote: Hi, I have the same libpng error when starting Opera 12.11 as already mentioned on this list. I happen to run KDE and ktrace shows me it crashes while reading icons like /usr/local/kde4/share/icons/oxygen/64x64/mimetypes/unknown.png. After renaming these icons so Opera does not find them it still prints 'libpng error: incorrect data check' but does not crash anymore. If I start without KDE integration there is no error anymore. You can do this by adding Dialog Toolkit=4 to the [File Selector] part of your opera*.ini. http://de.opera.com/support/usingopera/operaini/#file_selector Not an ideal solution, but at least I can read my e-mail again in Opera. I've added a note in UPDATING for this, thank you! -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID F0808380 ___ 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: apcupsd compile fails on 9-stable amd64
On Sat, 25 Aug 2012 14:01:09 -0600 (MDT) Warren Block wbl...@wonkity.com wrote: On Sat, 25 Aug 2012, Oleg Ginzburg wrote: On Saturday 25 August 2012 18:06:29 Warren Block wrote: Discovered last night that sysutils/apcupsd will not compile on 9-stable amd64 if the USB or SNMP options are enabled. It does compile on 8.3-stable i386. Stock gcc, not clang. ccache is installed, but not used for ports. Any suggestions? ... CXX src/apcupsd.c CXX src/apcnis.c LDsrc/apcupsd /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a(s nmp.o): In function `Snmp::VarBindList::VarBindList(Asn::Sequence)': snmp.cpp:(.text+0x7a8): undefined reference to `operator new[](unsigned long)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a( snmp.o): In function `Snmp::VarBindList::Append(Asn::ObjectId const, Snmp::Variable*)': snmp.cpp:(.text+0xdc9): undefined reference to `operator new[](unsigned long)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a( snmp.o): In function `Snmp::VarBindList::VarBindList(Asn::Sequence)': snmp.cpp:(.text+0xec8): undefined reference to `operator new[](unsigned long)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a( asn.o): In function `Asn::Sequence::assign(Asn::Sequence const)': asn.cpp:(.text+0x73d): undefined reference to `operator new[](unsigned long)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a( asn.o): In function `Asn::ObjectId::demarshal(unsigned char*, unsigned int)': asn.cpp:(.text+0x82b): undefined reference to `operator new[](unsigned long)' /usr/ports/sysutils/apcupsd/work/apcupsd-3.14.10/src/drivers/libdrivers.a( asn.o):asn.cpp:(.text+0x934): more undefined references to `operator new[](unsigned long)' follow Ive already register PR for this: http://www.freebsd.org/cgi/query- pr.cgi?pr=ports/170522 Sorry, saw that last night, but forgot about it. The fix works for me. Thanks! Thanks for confirming -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: Skype 4.0
On Fri, 15 Jun 2012 23:02:43 -0700 (PDT) Waitman Gobble uzi...@da3m0n8t3r.com wrote: dude like since MS bought it they haven't even released any non-win32 version. i agree, a different alternative to skype is better, and get your contacts to join up with that. If you don't count Mac, Android, and some other .. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: Skype 4.0
On Fri, 15 Jun 2012 17:11:03 -0400 Rich Neese r.ne...@gmail.com wrote: On 6/15/2012 5:08 PM, Robert Simmons wrote: On Fri, Jun 15, 2012 at 1:08 PM, Jerry je...@seibercom.net wrote: Skype 4.0 for Linux is now available. Is there any possibility of getting it ported to FreeBSD? The latest version in ports is only 2.x. I don't have time to do it right at the moment, but since this is pre-compiled binary software, updating the port yourself and sending the patches in with a PR would not be a complex task. I'm confident that you could do it. Start here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/quick-porting.html The URL for downloading the bugger is here: http://download.skype.com/linux/skype_static-4.0.0.7.tar.bz2 Good luck, and thanks in advance! It also needs to run, which it doesn't for lack of linux emulation things and some linux- ports. I just wish skype would get off their buts and make a bsd version. time to break code and make a opensource version 0 chances. As a market we're not significant at all for them. Even Linux isn't, not really. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: FreeBSD Ports conflicts checker
[ PLEASE don't top-post, ktnx ] On Tue, 05 Jun 2012 14:29:58 +0300 Sulev-Madis Silber madis...@hot.ee wrote: Well, I admit that this short summary was little too big. Bigger than the another report that regularly ends up in ports@ Maybe big maintainer groups need different approach to this. And this needs more refinement. I let things settle for a while and tell few weeks later what is left. With more sanity and size checks, maybe. Refined form of conflicts. This report already contains useful stuff but it's hard to spot currently. Port maintained by ports@ are unmaintained so there's no big maintainer group here; IMO you should send this kind of botmails to ports@ from time to time (each 2-4 weeks), eventually with some by-hand comments in it if that's the case. Else no one will know / fix these ports. Based on my experience of running QAT for some years: - $people will complain about noise - $people will complain about the way the mail is formatted (yeh, of course I have a few suggestion about that :D ) (in 90% of the cases, $people above would do much better to ssh freefall.FreeBSD.org tail -2 /etc/motd) - bugging people / lists on each run makes people ignore the issues My suggestion is to: - do a mass mailing (recap) each 6-8 weeks, - not send a mail on each run, except a commit was done to the respective ports since the lasts mail (in which case the problem should have been fixed) - avoid false-positives even if this way you risk missing some problems; 5% of false positives make people doubt the real 95% problems (generally speaking, getting right the last 5-10% is 90% of the work) - KEEP STATS. LOTS OF. if $port is broken for weeks and weeks, then we(portmgr@)'d like to know about it in order to find out what prevents it to be fixed and get it fixed. From a QA POV, I think your work is one of the best things that happened in the last years. THANK YOU for your work. (I'll be in touch in the next days). -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: net-im/skype-devel
On Tue, 5 Jun 2012 11:56:51 +0800 Martin Wilke m...@freebsd.org wrote: On Mon, 4 Jun 2012 23:41:05 +0300 Ion-Mihai Tetcu ite...@freebsd.org wrote: Last time I tested, yes, that was one of the problems. Current beta from skype is at .99, you could give it a try, but I don't expect anything better. And upcoming 3 is even worse. I tested already it doesn't work, because it requires libtiff.so.4. Yeh, I know. As with other non-trivial linux ports, problems arise from both linuxulator and linux_base ports. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: net-im/skype-devel
On Mon, 4 Jun 2012 19:50:52 +0200 (CEST) Juergen Lock n...@jelal.kn-bremen.de wrote: In article 20120604120054.GA1849@tiny you write: Hi, Hi! I run 10-CURRENT r235646 and CVS updated ports (both from May, 19); skype-2.1.0.81,1 is working fine, uncluding viedo: the port net-im/skype-devel still says, that video is broken; is there some pre-view to test or to help debugging? I'm not itetcu but... Skype is closed source so it's not easy to find out why video doesn't work with the version in net-im/skype-devel, but IIRC linux_kdump showed it's trying to use the Linux inotify syscall which is still missing in the Linuxolator. Is this the cause video doesn't work? Last time I tested, yes, that was one of the problems. Current beta from skype is at .99, you could give it a try, but I don't expect anything better. And upcoming 3 is even worse. Only those with the source know... Well, yeh. Trouble is linux version has the lowest priority (and the user base is constant, unlike the user base for the other versions); and while the skype devs are really nice people, there's a high level of institutional legal paranoia which doesn't help at all. So ... -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: port variants
On Sat, 14 Apr 2012 05:00:34 -0700 per...@pluto.rain.com wrote: Kevin Oberman kob6...@gmail.com wrote: While I think makefile-options is the way to go, I should also point out that for the specific case of emacs and X11, it is not used due to the very large differences. Other variants are handled via options, but there are separate emacs and emacs-nox11 ports. ... The port maintainer/developer has to make a call as to which approach is more practical, but I suspect portmgr@ will press for maximum use of makefile-options. Unfortunately we can't force anyone to use OPTIONS. Yet. I hope things will change once we get OPTIONS-NG in, since the new framework will address (AFAIK) all the objections people have against our current OPTIONS. One reason to use a slave port instead of an option is so that both configurations will be routinely build-tested, and corresponding packages made available. Any one port can have only one default configuration. Yes. We're lagging behind in this area. With the new OPTIONS and the next iteration of pkgNG, this will be hopefully solved. BUt it will take at least a year. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: Yikes: ports/157174: fix typos and small mistakes in various ports
On Wed, 15 Feb 2012 15:11:20 +0200 Alex Kozlov s...@rm-rf.kiev.ua wrote: On Wed, Feb 15, 2012 at 07:49:06AM -0500, Michael Scheidell wrote: On 2/15/12 7:15 AM, Alex Kozlov wrote: Many of those errors was already fixed, thanks to eadler@ I will upload updated list. can we get them all, and get them /correct/ before the port freeze? (thanks Alex.. wish I had seen the list earlier, ) Isn't ports tree go in a slush instead of full freeze during the release? Slush yes, but not yet. So it's ok committing this kind of things. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: Installing executables with generic names
On Tue, 14 Feb 2012 11:49:00 -0500
Michael Scheidell scheid...@freebsd.org wrote:
On 2/14/12 11:18 AM, Mikhail T. wrote:
On 14.02.2012 10:25, Michael Scheidell wrote:
EXAMPLESDIR
I thought, EXAMPLESDIR is for actual examples, such as source code,
not compiled and fully-functional executables... Indeed, the
directory is under ${PREFIX}/share -- which, according to hier(7)
is for architecture-independent files.
-min,
then, put them into EXAMPLESDIR/{arch}...
or put them anywhere you want.
No, if they are binaries they don't have any reason to be in
EXAMPLESDIR. The other idea of prefixing them is _much_ better.
--
IOnut - Un^d^dregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B
___
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: ports/164244: multimedia/mplayer: last update (1.0.r20111218) conflicts with devel/ncurses
On Thu, 19 Jan 2012 19:00:04 +0100 Thomas Zander thomas.e.zan...@googlemail.com wrote: But the takeaway is that we can't expect the PR submitters, or even port maintainers, to get anything right. It sure makes life easier when they do, but we can't take it for granted. As committers, we are that QA step. And we maintainers appreciate that there is a QA step represented by a committer. Trust me, I do! I'm calling it the safety belt. I found out how useful and relaxing it is while moving from maintianer/submitter to committer under mentorship to full commiter :) -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: multimedia/zoneminder: rc script runs mysql commands?
On Wed, 11 Jan 2012 20:14:18 + Michael Scheidell michael.scheid...@secnap.com wrote: We have the same problem with a commercial product. Is the user decided to pull a black cord Instead of a soft shut down, the next time a power it up, sometimes there is a race conditions between time out on the services that are looking to a running sequel server, and the database recovery. rc ordering is a good way to at least give me a hint which 1 needs to start first but has everyone has observed, it in a bit self cannot guarantee this service is running. you could do something funky with wait pid but you might not want the system to hang waiting for everything to start. some kind of passive wait loop 2 seconds wait loop 4 seconds wait loop 10 seconds wait loope 60 seconds wait loop 120 seconds but this is not a free bsd porting issue. Uostream would need to look at it. Yes, but at least some kind of check if the service actually started, some echo in the console / logging would be veyr good. From: owner-freebsd-po...@freebsd.org [owner-freebsd-po...@freebsd.org] on behalf of Ion-Mihai Tetcu [ite...@freebsd.org] Sent: Wednesday, January 11, 2012 2:47 PM To: Mark Felder Cc: freebsd-ports@freebsd.org Subject: Re: multimedia/zoneminder: rc script runs mysql commands? On Wed, 11 Jan 2012 12:41:27 -0600 Mark Felder f...@feld.me wrote: On Wed, 11 Jan 2012 12:16:45 -0600, Boris Samorodov b...@passap.ru wrote: The problem is: while start-up zoneminder is launched after mysql was started but is not responding yet. This, unfortunatelly, highlights perhaps our biggest problem with starting services. rc.d basically only *orders* the scripts - REQUIRE is just this service needs to be started after that one - AFTER is just a lax checkpoint in the booting sequence And if a script doesn't really start the service, for whatever reason, there's 0 feedback mandeted/provided by the framework. For short, while everything works OK, it's good enough. If not ... it's just misleading. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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 __ This email has been scanned and certified safe by SpammerTrap(r). For Information please see http://www.spammertrap.com/ __ -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: multimedia/zoneminder: rc script runs mysql commands?
On Wed, 11 Jan 2012 12:41:27 -0600 Mark Felder f...@feld.me wrote: On Wed, 11 Jan 2012 12:16:45 -0600, Boris Samorodov b...@passap.ru wrote: The problem is: while start-up zoneminder is launched after mysql was started but is not responding yet. Then zoneminder can't register it's cameras, etc. This hack was introduced to catch the moment when mysql really is operational and then start zoneminder. If someone has a solution -- you are welcome. Instead of hacking up zoneminder's rc script with further patches like pulling out the real mysql server, database, username and password perhaps we should see if we can get the mysql maintainer(s) to fix the mysql rc script so it doesn't exit until the service is fully fired up and functional? This, unfortunatelly, highlights perhaps our biggest problem with starting services. rc.d basically only *orders* the scripts - REQUIRE is just this service needs to be started after that one - AFTER is just a lax checkpoint in the booting sequence And if a script doesn't really start the service, for whatever reason, there's 0 feedback mandeted/provided by the framework. For short, while everything works OK, it's good enough. If not ... it's just misleading. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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] pkgng alpha2
On Tue, 13 Dec 2011 19:56:05 +0200 Andriy Gapon a...@freebsd.org wrote: on 13/12/2011 19:22 Julien Laffaye said the following: On 12/13/2011 06:16 PM, Andriy Gapon wrote: on 30/11/2011 22:32 Julien Laffaye said the following: [1] : https://github.com/pkgng/pkgng/issues [2] : https://github.com/pkgng/pkgng [3] : http://wiki.freebsd.org/pkgng [4] : http://people.freebsd.org/~bapt/pkgng-bsdcan2011.pdf [5] : http://wiki.freebsd.org/201110DevSummit/Ports?action=AttachFiledo=gettarget=pkgng-devsummit.pdf [6] : http://wiki.freebsd.org/201110DevSummit?action=AttachFiledo=gettarget=pkgng-devsummit-track.pdf Couple of questions/suggestions: 1. Do you plan to have a pkgng port to issue the preview releases pkgng? Current pkgng installation/bootstrap procedure is really easy, but the port would be even more convenient for prospective testers. Yes, this is planned. The ports will bootstrap pkgng. Great! The current idea is to have everything in ports so that we don't depend on the base OS for any kind of changes; we'll only have a bootstrap in base. One more step forward to decoupling ports from src releases. 2. Is there a public pre-built package repository with pkgng-format packages that could be used for testing and getting a taste of a packages-only pkgng-managed system? Unfortunately, no. I think I now have the resources to do that for the next CFT. But it will only be 9.0 amd64 I am afraid. We cant build packages for the entire matrix. I understand. Those would take an immense amount of compilation time and storage space. Storage and especially storage / propagation to mirrors are the biggest problems. After pkgNG goes in, we plan to switch HEAD to it and provide only pkgNG packages for it; then probably the same for 9-STABLE and further 9 releases, but we'll probably need to provide current style of pacakges during 9.x life time :( -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: pr# for 9-10 problem?
On Sat, 10 Dec 2011 09:35:03 -0500 Robert Huff roberth...@rcn.com wrote: Doug Barton writes: Read /usr/ports/UPDATING? If you mean 20110928 - that identifies the problem, and provides workarounds, but does not name the pr. What are you trying to accomplish? I have some machines that I would like to update, but would prefer to hold off until a non-workaround solution is in place. (Understanding this may take some time.) I would like to see the pr(s?) so I can understand what obstacles remain and when an acceptable solution might happen. We'll be doing full builds on pointyhat from time to time with the bsd.port.mk hack disabled to have a list of not-fixed ports and ping maintainers/upstream about fixing them. It's going to take a lot of time to get them all fixed upstream. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: Plan to add a bsd.pure.mk
On Thu, 10 Nov 2011 13:02:38 -0600
Zhihao Yuan lich...@gmail.com wrote:
Hi,
The PR which updates all pure-* ports was passed to portmgr for a long
time, since it seem that to put a
.if defined(USE_PURE)
.include ${PORTSDIR}/Mk/bsd.pure.mk
.endif
In bsd.port.mk may a be better choice. Though Pure is not as popular
as some languages like PHP or Python, but it does and it will have
more ports than like Go. To include bsd.pure.mk under Mk/ can lower 2
lines in ~20 ports (or I have to leave it under lang/pure's private
directory).
How many pure ports are there ATM?
--
IOnut - Un^d^dregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B
signature.asc
Description: PGP signature
Re: Small typos in COMMENT
Just go ahead and commit them all. Thanks.
On Sun, 13 Nov 2011 02:34:01 -0500
Eitan Adler li...@eitanadler.com wrote:
Hi,
The following ports have a small typo in the COMMENT line. Can you
please commit the change below or permit me to commit this patch?
Index: iso12083/Makefile
===
RCS file: /home/pcvs/ports/textproc/iso12083/Makefile,v
retrieving revision 1.14
diff -u -r1.14 Makefile
--- iso12083/Makefile 7 Jul 2003 11:51:38 - 1.14
+++ iso12083/Makefile 13 Nov 2011 07:29:32 -
@@ -15,7 +15,7 @@
EXTRACT_ONLY=# empty
MAINTAINER= kuriy...@freebsd.org
-COMMENT= SGML DTDs from the The Electronic Publishing Special
Interest Group +COMMENT= SGML DTDs from The Electronic
Publishing Special Interest Group
RUN_DEPENDS= ${XMLCATMGR}:${PORTSDIR}/textproc/xmlcatmgr
Index: jpilot-picsnvideos/Makefile
===
RCS file: /home/pcvs/ports/palm/jpilot-picsnvideos/Makefile,v
retrieving revision 1.4
diff -u -r1.4 Makefile
--- jpilot-picsnvideos/Makefile 23 Sep 2011 22:24:56
- 1.4 +++ jpilot-picsnvideos/Makefile 13 Nov 2011
07:29:32 - @@ -13,7 +13,7 @@
PKGNAMEPREFIX= jpilot-
MAINTAINER= sklau...@trimind.de
-COMMENT= JPilot plugin to to download photos and videos
+COMMENT= JPilot plugin to download photos and videos
RUN_DEPENDS= jpilot:${PORTSDIR}/palm/jpilot
BUILD_DEPENDS= jpilot:${PORTSDIR}/palm/jpilot
Index: noegnud-littlehack/Makefile
===
RCS file: /home/pcvs/ports/games/noegnud-littlehack/Makefile,v
retrieving revision 1.16
diff -u -r1.16 Makefile
--- noegnud-littlehack/Makefile 28 Mar 2010 06:35:23
- 1.16 +++ noegnud-littlehack/Makefile13 Nov 2011
07:29:32 - @@ -17,7 +17,7 @@
EXTRACT_ONLY=${DISTNAME}_linux_src-minimal${EXTRACT_SUFX}
MAINTAINER= llw...@infor.org
-COMMENT= The noeGNUd UI for the the LittleHack variation of
Nethack +COMMENT= The noeGNUd UI for the LittleHack variation
of Nethack
RUN_DEPENDS=
${LOCALBASE}/share/${NOEGNUDVERSION}/data/gui:${PORTSDIR}/games/noegnud-data
Index: p5-DBICx-Deploy/Makefile
===
RCS file: /home/pcvs/ports/databases/p5-DBICx-Deploy/Makefile,v
retrieving revision 1.6
diff -u -r1.6 Makefile
--- p5-DBICx-Deploy/Makefile 24 Sep 2011 22:02:35 -
1.6 +++ p5-DBICx-Deploy/Makefile 13 Nov 2011 07:29:32 -
@@ -14,7 +14,7 @@
PKGNAMEPREFIX= p5-
MAINTAINER= m...@freebsd.org
-COMMENT= Perl 5 module to deploy a a DBIx::Class schema
+COMMENT= Perl 5 module to deploy a DBIx::Class schema
BUILD_DEPENDS=
p5-DBIx-Class=0.07003:${PORTSDIR}/databases/p5-DBIx-Class \
p5-SQL-Translator=0:${PORTSDIR}/databases/p5-SQL-Translator \ Index:
p5-Rose-DBx-Object-MoreHelpers/Makefile
===
RCS
file: /home/pcvs/ports/databases/p5-Rose-DBx-Object-MoreHelpers/Makefile,v
retrieving revision 1.5 diff -u -r1.5 Makefile ---
p5-Rose-DBx-Object-MoreHelpers/Makefile 24 Sep 2010 00:44:18
- 1.5 +++ p5-Rose-DBx-Object-MoreHelpers/Makefile
13 Nov 2011 07:29:32 - @@ -14,7 +14,7 @@ PKGNAMEPREFIX= p5-
MAINTAINER= m...@freebsd.org
-COMMENT= Perl 5 module to deploy a a DBIx::Class schema
+COMMENT= Perl 5 module to deploy a DBIx::Class schema
RUN_DEPENDS=
p5-Rose-DB-Object=0.7730,1:${PORTSDIR}/databases/p5-Rose-DB-Object \
p5-Data-Dump=1.06:${PORTSDIR}/devel/p5-Data-Dump
Index: py-nevow/Makefile
===
RCS file: /home/pcvs/ports/www/py-nevow/Makefile,v
retrieving revision 1.17
diff -u -r1.17 Makefile
--- py-nevow/Makefile 26 Jul 2011 19:59:58 - 1.17
+++ py-nevow/Makefile 13 Nov 2011 07:29:32 -
@@ -16,7 +16,7 @@
EXTRACT_SUFX=.tar.gz?format=raw
MAINTAINER= ni...@freebsd.org
-COMMENT= A web application templating system, based on the
the Twisted Woven +COMMENT= A web application templating
system, based on the Twisted Woven
BROKEN= does not build
--
IOnut - Un^d^dregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B
___
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: [UPDATE] Re: Update on ports on 10.0
On Thu, 27 Oct 2011 15:42:00 +0400 Ruslan Mahmatkhanov cvs-...@yandex.ru wrote: Erwin Lansing wrote on 27.10.2011 14:21: On Fri, Oct 21, 2011 at 12:44:34PM +0300, Ion-Mihai Tetcu wrote: What, on the other hand, makes sense is to have the fix that should include: a) a KNOB (WITH_FBSD10_FIX or similar), b) that only is run from bsd.port.mk when OSVERSION100 c) runs the latest version of the above patch. The KNOB's existence allow us to turn on the fix only for broken ports, and easily know what these broken ports are -- so we can poke maintainers from time to time about upstream fixes, ... Erwin is currently running a build on i386-10 with this and the following patches: - bsd.port.mk patch from beat (based on ed@, jilles@ and stas@ patches) - python patch from beat - python patch from linimon - WITH_FBSD10_FIX in: - textproc/expat2 - devel/pcre - devel/libtool - audio/libogg Results by Monday. These patches have now been committed to the tree, notably with lang/python27 missing in the above list but was included as well. There have been some proposals already and we can now incrementally improve the workaround and, more importantly, start fixing individual ports. Please note that the patch tries to balance between being a general enough fix to make it easy to get a working system running while not just swiping the whole issue under the rug and forget about it until the next release cycle. Make sure to send any fixes upstream to the hack can be removed from the ports again. Thanks for all your patience and thanks for all those involved, especially beat who sent many patches and improvements. Erwin About devel/libtool fix. Why to not update it to 2.4.2 where this was fixed upstream? I mean http://bugs.freebsd.org/162012 We probably need an other set of -exps for that, given how many ports depends on it, and I don't think we have the time for that before the release. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: [UPDATE] Re: Update on ports on 10.0
On Wed, 19 Oct 2011 11:31:36 +0300 Ion-Mihai Tetcu ite...@freebsd.org wrote: On Wed, 19 Oct 2011 01:04:20 -0700 Stanislav Sedov s...@freebsd.org wrote: On Wed, 19 Oct 2011 10:59:38 +0300 Ion-Mihai Tetcu ite...@freebsd.org mentioned: Unfortunately we don't seem to have any other way to go, for the (and yes, I hate the idea) big majority of the ports. The fix is basically identical, so it doesn't make sense to have a zillion of patch files in a zillion of ports. What, on the other hand, makes sense is to have the fix that should include: a) a KNOB (WITH_FBSD10_FIX or similar), b) that only is run from bsd.port.mk when OSVERSION100 c) runs the latest version of the above patch. The KNOB's existence allow us to turn on the fix only for broken ports, and easily know what these broken ports are -- so we can poke maintainers from time to time about upstream fixes, ... Sounds good to me. A few more days. Erwin is currently running a build on i386-10 with this and the following patches: - bsd.port.mk patch from beat (based on ed@, jilles@ and stas@ patches) - python patch from beat - python patch from linimon - WITH_FBSD10_FIX in: - textproc/expat2 - devel/pcre - devel/libtool - audio/libogg Results by Monday. If everything goes OK, we'll commit the patch. We're not sure if we'll have enough time for running other -exps to find the broken ports that need the fix before we need to concentrate on building the packages for the release, but we'll try. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: [UPDATE] Re: Update on ports on 10.0
On Tue, 18 Oct 2011 01:01:00 -0700 Stanislav Sedov s...@freebsd.org wrote: On Tue, 18 Oct 2011 10:50:48 +0300 Ion-Mihai Tetcu ite...@freebsd.org mentioned: Did you do a full run with the patch? Can you provide the list of ports that aren't fixed by the patch and the exact patch you used? Thanks. Did you? I'm not the one sitting on the cluster... Not exactly sitting idle, the cluster has been maxed out in the last days with other exps also besides the regular package building. Several people provided the patch already, a version of it was present in the bsd.port.mk as well at one point of time. dougb@ nicely summarized it in one of his emails. Yes, I know. I was just asking since you said it fixed 99% of the ports ... It'd be nice to do an exp run with the patch mentioned and see if it breaks any ports and how many ports it fixes instead of doing any kind of educated guesswork (in my opinion). Well, actually 3 full runs would be needed: one on 9, one on 10 patched and one not patched, all with the same PT, to see what the differences are. (Or 2 on 10 one with uname set to 9 and one with the patch). Having this knob in the tree will help people to actually go about fixing the ports in the tree. Yes, we'll get there. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: [UPDATE] Re: Update on ports on 10.0
[ slightly reordered ] On Wed, 19 Oct 2011 09:31:46 +1100 Peter Jeremy peterjer...@acm.org wrote: [trimming cc list] On 2011-Oct-17 13:51:30 -0700, Stanislav Sedov s...@freebsd.org wrote: ones (like GCC). So why not commit that patch as a KNOB to bsd.port.mk like it was initially proposed and let people use it in individual ports makefiles to fix them (and portmgr@ can commit the initial bunch of these knobs)? This is the easiest thing you can do now, and you will be able to abandon it when the better solution is available (which is unlikely). Once hackish work-arounds get committed, it is extremely difficult to root them out. The last time the project included a temporary hack to assist with a similar problem (the aout to ELF migration in FreeBSD 3), it took more than a decade to get the hack out of base and after 13 years, there are still 71 ports (by my count) with local work-arounds. Given the debian/ubuntu release schedule, this is not going to happen earlier that 1-2 years from now, and Based on the objformat mess, whatever is done will hang around in the tree for at least a decade so we are far better off spending some time now to come up with the best solution, rather than quickly committing a work-around that we spend the next decade regretting. Unfortunately we don't seem to have any other way to go, for the big majority of the ports. The fix is basically identical, so it doesn't make sense to have a zillion of patch files in a zillion of ports. What, on the other hand, makes sense is to have the fix that should include: a) a KNOB (WITH_FBSD10_FIX or similar), b) that only is run from bsd.port.mk when OSVERSION100 c) runs the latest version of the above patch. The KNOB's existence allow us to turn on the fix only for broken ports, and easily know what these broken ports are -- so we can poke maintainers from time to time about upstream fixes, ... There are exceptions, e.g. python and perl. WRT your submit upstream comment, personanlly, I'd argue against this: Ports are never going to get fixed unless we advise the upstream maintainer that there is a problem. this is not the upstream maintainer's problem, it the buggy tools they use Unfortunately, we are unlikely to convince many people that GNU autocr*p is broken by design. But it _is_ the upstream maintainer's problem that they chose to use buggy/broken tools. to generate the configure scripts, so until the fixed version of libtool is available in all major distributions and widely installed, they're not going to replace it or patch locally. A reasonable approach would be to come up with fixes to libtool and the rest of autocr*p and get them applied to the master versions. Then go to the upstream maintainers with something along the lines of your foobar-1.2.3 will not work on FreeBSD 10 due to bugs in libtool and/or autocr*p. This has been in version X of those tools. If you are unable te update, could you please apply the following patch locally. Of course, this only applies to the latest version, old versions are going to need to be patched in the ports tree. Presumably $UPSTREAM wants it software to be able to build on FreeBSD even outside the PT, especially if this doesn't imply much work on his part. Whatever action we take will your patches/requests sent could potentially cause them to abandon FreeBSD support altogether requiring a lot of work to maintain which will be totally understandable. I don't see how this follows. It's no different to upstreaming any other FreeBSD-specific change. Yep. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: [UPDATE] Re: Update on ports on 10.0
On Wed, 19 Oct 2011 01:04:20 -0700 Stanislav Sedov s...@freebsd.org wrote: On Wed, 19 Oct 2011 10:59:38 +0300 Ion-Mihai Tetcu ite...@freebsd.org mentioned: Unfortunately we don't seem to have any other way to go, for the (and yes, I hate the idea) big majority of the ports. The fix is basically identical, so it doesn't make sense to have a zillion of patch files in a zillion of ports. What, on the other hand, makes sense is to have the fix that should include: a) a KNOB (WITH_FBSD10_FIX or similar), b) that only is run from bsd.port.mk when OSVERSION100 c) runs the latest version of the above patch. The KNOB's existence allow us to turn on the fix only for broken ports, and easily know what these broken ports are -- so we can poke maintainers from time to time about upstream fixes, ... Sounds good to me. A few more days. Presumably $UPSTREAM wants it software to be able to build on FreeBSD even outside the PT, especially if this doesn't imply much work on his part. You'd be surprized how many of them do not care about FreeBSD altogether. Even if you send them patches. Oh, I know, believe I know. But that's not the majority, and anyway it should stop us trying to do the right thing. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: configure: error: working directory cannot be determined
On Wed, 19 Oct 2011 11:58:40 +0100 Anton Shterenlikht me...@bristol.ac.uk wrote: On amd64 with the newvers.sh fix to 9.9 (9.9-CURRENT #2 r226525M:): === Configuring for libtool-2.4_1 configure: error: working directory cannot be determined === Script configure failed unexpectedly. Please report the problem to autoto...@freebsd.org [maintainer] and attach the /usr/ports/devel/libtool/work/libtool-2.4/config.log including the There is no config.log, but there is ls.core. I get this configure error on every port, not just libtool. #1 update your ports #2 Please wait a few days #3 check this lists' archives for the last week or so. Ktnx, -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: UPDATING 20111016 and KDE3
On Mon, 17 Oct 2011 20:13:30 +0200 Alberto Villa avi...@freebsd.org wrote: On Mon, Oct 17, 2011 at 7:11 PM, Ion-Mihai Tetcu ite...@freebsd.org wrote: If you have both kdenetwork3 and 4, well, I don't know. You can try proceeding with that step and seeing if kdenetwork3 still works, and report back. I thought it was quite unlikely that people had kdenetwork3 and 4 installed at the same time. Should this be a problem, I'll end up making it optional in kdenetwork4. Please do, I have them both. I have some problems doing it at the moment. rakuco/makc, can you test a fix for this? itetcu: did you try doing the replacement and seeing if kdenetwork3 still works? No, I'll try sometime this week. -- IOnut ___ 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: [UPDATE] Re: Update on ports on 10.0
On Mon, 17 Oct 2011 23:52:54 + Bjoern A. Zeeb bzeeb-li...@lists.zabbadoz.net wrote: On 17. Oct 2011, at 20:51 , Stanislav Sedov wrote: Hi, I shrinked that Cc: list dramatically. Thanks; I Cc'ed all maintainers of those high-profile ports. As a new update, we're now running an other -exp with jpeg fixed. On Mon, 17 Oct 2011 15:35:51 +0300 Ion-Mihai Tetcu ite...@freebsd.org mentioned: Here's a little status update: We iterated through a few -exp runs (basically for ports/161404 -- committed and ports/161431 -- skv@ any problem with it?). With those two we can build around 7k packages. The majority of the rest can't be built because of a few high profile ports that don't package: expat (6581), curl (975), jpeg(5057), lcms(1080), libiconv(11180), libltdl(1187), libogg(1947), pcre(5737), python27(5935). http://pointyhat.freebsd.org/errorlogs/i386-10-latest/ What we'd like to do next is see how many ports we can package after individually fixing those above. This will require a few other -exps since undoubtedly we'll find other highly-depended-on ports broken that weren't tried because of the blockers above. It doesn't require an exp-run to understand that you won't move much further with just fixinng these ports. Well, there was a significant update from ~2800 to ~7000 ports by just fixing 2 or 3? I think understanding these and handling them in a well defined manner is a good idea. And we need to know which are broken and which aren't. patching similar to the patch Ed, Doug and other people proposed. Actually, that sed one-liner fixed like 99% of the ports in tree, Did you do a full run with the patch? Can you provide the list of ports that aren't fixed by the patch and the exact patch you used? Thanks. excluding some complex ones (like GCC). So why not commit that patch as a KNOB to bsd.port.mk like it was initially proposed and let people use it in individual ports makefiles to fix them (and portmgr@ can commit the initial bunch of these knobs)? This is the easiest thing you can do now, and you will be able to abandon it when the better solution is available (which is unlikely). I think that's what he was saying as a possible next step. If they have the cycles currently while waiting for RC1 to happen let them do it; we are talking in having things within a month not in spring next year already. I would assume that the aforementioned patch might go into the framework, would only be applied if a) OSVERSION=10... and b) the port has a knob that says I need this to run. Yes. WRT your submit upstream comment, personanlly, I'd argue against this: We damn need it; they need to regen the stuff; it's going to take months if not years to get 80% to that point and a couple of projects might be dead and we might want to use a local patch then but the sed-KNOB is a bandaid that must die again. I would argue that no port must add the KNOB (once it would exist, should it) without having notified upstream. And you might know a lot better than I do but ideally there would be a new official libtool release before that and ideally the libtool people would have by now fixed all the !FreeBSD similar cases... Hopefully so. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: [UPDATE] Re: Update on ports on 10.0
On Tue, 18 Oct 2011 10:50:48 +0300 Ion-Mihai Tetcu ite...@freebsd.org wrote: On Mon, 17 Oct 2011 23:52:54 + Bjoern A. Zeeb bzeeb-li...@lists.zabbadoz.net wrote: On 17. Oct 2011, at 20:51 , Stanislav Sedov wrote: Hi, I shrinked that Cc: list dramatically. Thanks; I Cc'ed all maintainers of those high-profile ports. As a new update, we're now running an other -exp with jpeg fixed expat also -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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
[UPDATE] Re: Update on ports on 10.0
On Tue, 11 Oct 2011 08:36:03 +0200 Erwin Lansing er...@freebsd.org wrote: Since the release has been pushed back some more since the last mail, we do have some time to test a possible fix for the issues we're seeing with libtool on FreeBSD 10.0. However, fixing libtool is only part of the problem as hundreds, if not thousands, of ports roll their own detection and need to be fixed individually. We are currently running a fixed libtool (ports/161404) to assess how many ports are fixed by this patch and how many need to be patches manually before deciding how to move forward. Other options include the big find/grep/awk solution that has been posted several times and fiddling with uname to go to FreeBSD 9.99 for a while, while ports can be fixed. Hopefully, we can move forward in a day or two, but needless to say this needs a lot of testing both on 10.0 and earlier releases so we are sure we don't break backwards compatability, especially on 9.0 that is soon to be released. For those that cannot wait a few days, several patches have been proposed on the lists, of which dougb's seems most complete, so I recommend applying one of those locally. Please note that these are not tested widely and may break when the final fix is committed. To conclude with some fun facts, only 232 ports break on HEAD currently. Unfortunately, some of these are pretty high profile and prevent almost 19.000 other ports from building, leaving only slighty more than 3000 ports to build successfully. Here's a little status update: We iterated through a few -exp runs (basically for ports/161404 -- committed and ports/161431 -- skv@ any problem with it?). With those two we can build around 7k packages. The majority of the rest can't be built because of a few high profile ports that don't package: expat (6581), curl (975), jpeg(5057), lcms(1080), libiconv(11180), libltdl(1187), libogg(1947), pcre(5737), python27(5935). http://pointyhat.freebsd.org/errorlogs/i386-10-latest/ What we'd like to do next is see how many ports we can package after individually fixing those above. This will require a few other -exps since undoubtedly we'll find other highly-depended-on ports broken that weren't tried because of the blockers above. Depending on this number and how long the whole process will take, we can decide what solution to adopt. If possible we'd like to avoid the big hammer of an uname fiddle or find/grep/sed/... (which most probably won't work for all ports anyway, irrespective of how smart it will be). If we need to adopt one of these hacks, it will be via some conditional KNOB in each port Makefile, in order to have an easy way to know which ports are fixed and which not, and an easy way to turn it off for test builds without it in the future. Basically we do not want to shove the dirt under the carpet, were it will rot for years. YOU can help by sending portmgr@ patches for above ports (or any other you know is broken) for the next -exp run. And PLEASE, pretty please once you have a patch that fixes this problem submit it upstream and bug upstream about it. (committers: please check this is the case when committing a patch from a PR). Thanks! -- IOnut ___ 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: UPDATING 20111016 and KDE3
On Mon, 17 Oct 2011 10:08:57 +0200 Alberto Villa avi...@freebsd.org wrote: On Mon, Oct 17, 2011 at 9:15 AM, Andrea Venturoli m...@netfence.it wrote: Using KDE3, I have ortp as a dependency of kdenetwork. Should I follow the above or is it ok only for KDE4? Is it needed? Would it harm anything? linphone-base is required by kdenetwork4, if you don't have it you can skip that line. I'll add it to UPDATING, thanks. If you have both kdenetwork3 and 4, well, I don't know. You can try proceeding with that step and seeing if kdenetwork3 still works, and report back. I thought it was quite unlikely that people had kdenetwork3 and 4 installed at the same time. Should this be a problem, I'll end up making it optional in kdenetwork4. Please do, I have them both. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: Ports maintrainer mode?
On Sun, 16 Oct 2011 23:46:01 +1100 Alexey Golodov nirnroot.free...@gmail.com wrote: Looking through the ports, I see that sometimes maintrainers include in Makefile block with actions for maintrain port. There are different ways to define it (starting with MAINTRAINER_MODE in devel/git, and ends if user = $maintrainer_username) Probably, this feature should be unify and added to ports system? No. These are NOT public vars / targets; you shouldn't relay on any kind of behavior in any way, nor should you set the var or use maintainer targets. This is just something for that particular port and maintainer convenience. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Thank YOU [1] ...
... for helping me set my priorities strait. [2] It used to be fun to be here. I understand that, in general, people want to help. I understand that there can be a lot of useful input from people that actually do nothing or next to nothing in terms of coding, documenting and so on. I understand that perfectly reasonable and intelligent people might differ about various issues. It used to be good being here. What I CAN NOT understand is when people start insulting other people from the community. This is the point where my understanding and sympathy stops. PLEASE take a break. Go back on vacation. Whatever it takes to cool down. Come back in two weeks and think it over. Be polite. At very least be polite. Curb your sarcasm. No one is after *you*. No one wants to sink the FreeBSD ship. The opposite. It used to be fun to be here. It used to be good. NOT ANYMORE. I don't see what you'll gain when the 90% of top very active committers [3] (think gnome, think kde, thing office, think infrastructure, think $little_ports that 3 people use) dread to open freebsd-ports mail folder; when after reading a couple of messages they'd rather go drink something, watch TV, or whatever, instead of doing something for FreeBSD. You disagree with this or that or the other one? Put a team together or be the lone warrior and start DOING something. Be clear, succinct and, again, POLITE when you write about your new project. You can convince the others? You know how to do it better? You don't know how do to it better, but you think you can motive and manage people that do know? You can take all our work, for FREE, under the most permissive license out there. Fork. Do it better; for others; for you; for us; for me. The rest of you, please ssh freefall.freebsd.org tail -2 /etc/motd and keep up the good work. [1] YOU (plural). I shouldn't need to tell you who you are. I won't. You demotivated me more that enough. [3] Just in case you were wondering, it's a real number, not something I came up with. It used to be fun to be here. It used to be good. It USED to be. [2] No, I'm not going away. I put to much work and time in FreeBSD. But, for the foreseeable future, if you need to contact me about my ports, or other work, or anything else, mail me directly; I won't be reading this list. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B ___ 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: ruby and amarok - dead lock?
On Tue, 23 Aug 2011 22:57:11 +0200 Heino Tiedemann rotkaps_spam_t...@gmx.de wrote: Oliver Heesakkers free...@heesakkers.info wrote: Op dinsdag 23 augustus 2011 17:22:07 schreef Heino Tiedemann: Hi There ist is like a bite in your own ass (dead lock): [UODATING]: The default ruby version has been updated to 1.9. Please rebuild all ports that [AMAROK] BROKEN= does not build with ruby 1.9 What To do? Switch to audio/amarok-kde4. Bad idea. +1 I feel the kde4 version lost everything that made amarok unique. That meins complete KDE switch. For me too. And honestly, if I want something that looks like vista, I can install windows 7 :) At least recent kde4 versions are snapier that the fist ones, but I still don't feel motivated to move (which brings on the question of what WM I'll be using in a year or two). Unless it's an easy fix, I doubt these kde3/qt3 programs will get the attention needed to fix it. .. unfortunately :( Yep. -- Ion-Mihai Tetcu io...@tetcu.info ___ 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: PREFIX is not honored for dependencies
On Sat, 06 Aug 2011 12:40:39 +0400 Boris Samorodov b...@ipt.ru wrote: [ .. ] BTW, QAT was used to do experimental runs with non-default PREFIX. Those reports were very useful. [ .. ] Yeh, that was a second server QATty, which used to run on some old hardware of mine, toasted long since. I'm trying to bring a few QAT instances back on-line (time permitting, sigh), one of which would have a totally non-default config. (The idea being to present in an obvious way what fails for what reason). -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: 'FreshPorts -- FAQ' international
On Wed, 22 Jun 2011 14:16:26 +0300 Alyona Lompar alyona.lom...@techie.com wrote: Hi! I'm willing to translate page located at http://www.freshports.org/faq.php to the Belorussian language (my mother tongue). What I'm asking for is your written permission, so you don't mind after I'll post the translation to my blog. The translation is intended only for web, no print copies planned. [ .. ] You should contact the ownerk of that site, Dan Langille d...@langille.org. -- Ion-Mihai Tetcu ite...@freebsd.org ___ 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: OpenTTD
On Wed, 22 Jun 2011 09:56:55 +0100 Chris Rees cr...@freebsd.org wrote: 2011/6/22 Alexey Dokuchaev da...@freebsd.org: On Wed, Jun 22, 2011 at 10:33:14AM +0400, Ilya A. Arkhipov wrote: Ok i rewrite patch and do with argument, and write patch to portlint ;) Wow, if you could write a patch to portlint that is would correctly suggest that MAINTAINER/COMMENT/LICENSE should be grouped together, and FOO_DEPENDS would be closed to USE_BAR knobs, I'd be very grateful! Just to make myself clear on this issue: COMMENT/LICENSE are general software information, FOO_DEPENDS and USE_BAR knobs both specify dependencies (that is, package-related stuff). I believe that it does not make sence to mix them, hence LICENSE should be defined before _DEPENDS, not after. I agree 110% with this. It confused me a while ago when I started to use LICENSE, but I think the general acceptance is that we should have: PORTNAME PORTVERSION etc MAINTAINER COMMENT LICENSE So license in a separate block; you can have several license lines making the MAINTAINER/COMMENT block unnecessarily large. Not too sure about keeping _DEPENDS with USE; there're additional variables often set with USE, perhaps a block for _DEPENDS and then USE etc underneath? (could follow with USERS/GROUPS). Example: PORTNAME PORTVERSION etc MAINTAINER COMMENT LICENSE LIB_DEPENDS= BUILD_DEPENDS= RUN_DEPENDS= USE_FOO FOO_ARGS USE_BAR USERS GROUPS *dEPENDS and USE* are really the same thing, dependencies (with, maybe, some rare exceptions). So I'd say they should go together. -- Ion-Mihai Tetcu ite...@freebsd.org ___ 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: portlint(1) knobs order: let's make things more logical
Alexey Dokuchaev da...@freebsd.org wrote: On Wed, Jun 22, 2011 at 04:02:33PM +0300, Ion-Mihai Tetcu wrote: *DEPENDS and USE* are really the same thing, dependencies (with, maybe, some rare exceptions). So I'd say they should go together. Precisely. That was my original concern (that currently, portlint advises to put LICENSE knob between them). I think most people would agree that this behavior goes against common sense and should be fixed. ./danfe +1 -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. ___ 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
net/sendemail fails with perl 5.14 (INET6) (was: Re: net/sendemail fails after updating Perl)
On Sun, 22 May 2011 21:21:44 +0900 Hajimu UMEMOTO u...@mahoroba.org wrote: Hi, On Sat, 21 May 2011 08:36:45 -0400 Jerry je...@seibercom.net said: jerry The port: /net/sendemail builds fine after the update to jerry Perl; however, it no longer runs. It terminates with this jerry error message: jerry Subroutine IO::Socket::INET6::sockaddr_in6 redefined jerry at /usr/local/lib/perl5/5.14.0/Exporter.pm line 67. jerry at /usr/local/lib/perl5/site_perl/5.14.0/IO/Socket/INET6.pm jerry line 21 Perl 5.14 has its own IPv6 support. I suspect it is conflict with p5-IO-Socket-INET6. No, a nice thing about this port is that it's self contained (the only two optional depends, for TLS, are p5-IO-Socket-SSL and p5-Crypt-SSLeay). The port is at the latest version (released in 2009, h). Since perl 5.14 is not the default, I marked it broken for now and ping upstream to see if there's still any active development. I don't intend to maintain this as a fork ; anyone wanting to take over maintainership has just to ping me. I found other compatibility issue that 5.14 deesn't has sv_undef, sv_yes nor sv_no, anymore. It causes that cyrus-imapd doesn't build with 5.14. Perhaps, there are more ports which are affected by this issue. Any way to detect this at build time? We could od a run on pointy if that's the case, and at least have a list of problems. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: net-p2p/bitcoin fails to install
On Sat, 21 May 2011 20:36:18 +0200
Torfinn Ingolfsen tin...@gmail.com wrote:
Hello,
net-p2p/bitcoin (currently 0.3.21) fails, it tries to install
wxgtk2-2.9.1 even if that one is already installed
[ .. ]
The actual problem is this:
=== bitcoin-0.3.21 depends on executable: include/wx-2.9/wx/aboutdlg.h - not
found
Since the port is maintained, CC'ing the maintainer would have helped.
Please try the patch below and let us know if it fixes the problem:
Index: Makefile
===
RCS file: /home/pcvs/ports/net-p2p/bitcoin/Makefile,v
retrieving revision 1.1
diff -u -r1.1 Makefile
--- Makefile 20 May 2011 22:50:37 - 1.1
+++ Makefile 22 May 2011 13:04:54 -
@@ -38,7 +38,7 @@
#USE_WX=2.9+
-BUILD_DEPENDS+= include/wx-2.9/wx/aboutdlg.h:${PORTSDIR}/x11-toolkits/wxgtk29
+BUILD_DEPENDS+=
${LOCALBASE}/include/wx-2.9/wx/aboutdlg.h:${PORTSDIR}/x11-toolkits/wxgtk29
WX_CONFIG= ${LOCALBASE}/bin/wxgtk2u-2.9-config
PLIST_FILES=bitcoin
--
IOnut - Un^d^dregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B
signature.asc
Description: PGP signature
Re: Optional Patches
On Wed, 18 May 2011 19:01:31 -0400 Matthew Pounsett m...@conundrum.com wrote: Based on the responses here it sounds like I've been doing nothing wrong so I played around a bit more. I guess in my testing there must've been some combination of things I didn't get right... I did a bunch more testing and eventually I made it work doing exactly what I've been doing, except for the location of the ifdef. It turns out that in order to make this work, the .if define must appear below where bsd.port.pre.mk is included. If it occurs above that, I guess the definition of .if doesn't exist yet and so the block doesn't get run at all. Yes, or you need to use bsd.options.mk. I don't recall seeing this restriction mentioned in the porters' handbook, but perhaps I missed it. It is documented in PH 5.11.2.2 Syntax -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: net-p2p/bitcoin fails to install
On Sun, 22 May 2011 16:01:37 +0200
Thierry Thomas thie...@freebsd.org wrote:
On sun 22 mai 11 at 15:07:31 +0200, Ion-Mihai Tetcu
ite...@freebsd.org wrote:
Index: Makefile
===
RCS file: /home/pcvs/ports/net-p2p/bitcoin/Makefile,v
retrieving revision 1.1
diff -u -r1.1 Makefile
--- Makefile 20 May 2011 22:50:37 - 1.1
+++ Makefile 22 May 2011 13:04:54 -
@@ -38,7 +38,7 @@
#USE_WX=2.9+
-BUILD_DEPENDS+=
include/wx-2.9/wx/aboutdlg.h:${PORTSDIR}/x11-toolkits/wxgtk29
+BUILD_DEPENDS+=
${LOCALBASE}/include/wx-2.9/wx/aboutdlg.h:${PORTSDIR}/x11-toolkits/wxgtk29
WX_CONFIG= ${LOCALBASE}/bin/wxgtk2u-2.9-config
PLIST_FILES=bitcoin
Yet better: wxgtk29 should be handled by ports/Mk/bsd.wx.mk
(alepulver Cc:ed')
Seen that commented out in the Makefile, so I assumed there was some
specific reason for it.
--
IOnut - Un^d^dregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B
signature.asc
Description: PGP signature
Re: Skype with sound and video support :)
On Tue, 17 May 2011 21:46:14 +0200 Alexander Leidinger alexan...@leidinger.net wrote: On Tue, 17 May 2011 09:01:41 -0700 Kevin Oberman ober...@es.net wrote: Please put the information in this message (or at least most of it) into ports/UPDATING so a few less people running old kernels will be bitten by the installation of the new Skype port. And what about a wiki page? This way we can extend it in case something important is uncovered. I'm not opposed to it, but I don't see the need for it at this time. (Plus, I'd like to keep everything inside the port - hence the longish pkg-message - less steps to go through this way). -- Ion-Mihai Tetcu ite...@freebsd.org ___ 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: Skype with sound and video support :)
On Tue, 17 May 2011 09:01:41 -0700 Kevin Oberman ober...@es.net wrote: Date: Tue, 17 May 2011 10:38:58 +0300 From: Ion-Mihai Tetcu ite...@freebsd.org Sender: owner-freebsd-emulat...@freebsd.org Hi, As you may have noticed skype ports were updated a few days ago. All skype ports were moved to net-im/: - skype12: unchanged, very old version (for FreeBSD 6) - skype20: last version with OSS support, that used to live in net/skype; the DISTFILE is gone from the vendor but if you happen to have it it would be a way of having sound w/o a need to upgrade your base OS - [RECOMANDED] skype: currently at 2.1.0.81 and the best supported - skype-devel: currently at 2.2.0.25, sounds is OK, video doesn't work In order to run either skype or skype-devel with fully working sound you need: - to run fc10 (most probably, please report what you can run with fc4): (OVERRIDE_LINUX_BASE_PORT=f10,OVERRIDE_LINUX_NONBASE_PORTS=f10 in /etc/make.conf for systems that doesn't have it as default) - In order for Skype to work OK, you need your kernel and modules to be: - post 2011-05-03 in on HEAD - post 2011-05-08 in on 7,8-STABLE The port tries to catch if your system version is too old, but there's a ~3months window where because of a lack of OSVERSION bump, this is not possible. So please check; and PLEAE READ THE PKG_MESSAGE for setup details. For how to update your kernel/world, see: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig.html IF YOUR OSVERSION IS NOT NEW ENOUGH, SOUND (ESPECIALLY MIC) WON'T WORK. If you run into problems, at very least we need to know the output of: $ uname -a; sysctl compat.linux | head -2; grep OVERRIDE_LINUX_ /etc/make.conf; cat /compat/linux/etc/alsa/pcm/pcm-oss.conf the skype version you are using, and hardware details (eg. webcam) if related. I most probably will ignore any mail not containing this info since without it it's impossible to help. Please test your sound /video setup outside skype before blaming skype / mailing me. Many thanks for all of the work that went into getting a modern version of Skype working! Please put the information in this message (or at least most of it) into ports/UPDATING so a few less people running old kernels will be bitten by the installation of the new Skype port. Well, the same (and more) is in the pkg-message also. But OK, I will, ports/UPDATING is cheap. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: Skype with sound and video support :)
On Tue, 17 May 2011 09:37:03 -0700 Ted Faber fa...@isi.edu wrote: On Tue, May 17, 2011 at 07:28:35PM +0300, Ion-Mihai Tetcu wrote: But OK, I will, ports/UPDATING is cheap. And appreciated. Done after sending the mail :) -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: skype - microphone
On Sun, 15 May 2011 17:34:40 +0300 Andriy Gapon a...@freebsd.org wrote: on 15/05/2011 17:30 ajtiM said the following: H! I was stupid and update Skype to version 2.1.0.81and it is unusible now. And what is the other problem I don't have previous version which worked. What is a problem: my system is FreeBSD 8.2-RELEASE #0, KDE 4.6.2. Skype start, I have a sound, I hear ringing if someone call me, I can call but nobody hear me. Microphone was o.k. on the version 2.0 but now doesn't work. I have the same settings as before but nothing. Nothing is wrong with microphone because sound editor Audacity works and level of mic are okay too. I play with /compat/etc/alsa/pcm.conf but nothing. Thanks in advance. You need a specific commit to be present in your kernel. Take a look at IGNORE lines in the latest net-im/skype port. Take a look at the pkg-message and make sure your you have the kernel/modules build from the required sources. Ans post more details. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: x11/nvidia-driver: cc1: error: /src: No such file or directory
On Mon, 09 May 2011 21:18:20 +0200 Hartmann, O. ohart...@mail.zedat.fu-berlin.de wrote: Port x11/nvidia-driver fails with the the following error. This error obviously was introduced within the updates of the last few days, since building the specific port was possible before the last weekend. Does anyone has an idea? Regards, Oliver === Vulnerability check disabled, database not found === License NVIDIA accepted by the user === Found saved configuration for nvidia-driver-270.41.06 === Extracting for nvidia-driver-256.53 = SHA256 Checksum OK for NVIDIA-FreeBSD-x86_64-256.53.tar.gz. === Patching for nvidia-driver-256.53 === nvidia-driver-256.53 depends on shared library: GL.1 - found === Configuring for nvidia-driver-256.53 === Building for nvidia-driver-256.53 === src (all) @ - /usr/src/sys machine - /usr/src/sys/amd64/include x86 - /usr/src/sys/x86/include awk -f @/tools/makeobjops.awk @/kern/device_if.m -h awk -f @/tools/makeobjops.awk @/kern/bus_if.m -h awk -f @/tools/makeobjops.awk @/dev/pci/pci_if.m -h awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -p awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -q awk -f @/tools/vnode_if.awk @/kern/vnode_if.src -h cc -O2 -pipe -march=native -DNV_VERSION_STRING=\256.53\ -D__KERNEL__ -DNVRM -O -mcmodel=kernel -mno-red-zone -UDEBUG -U_DEBUG -DNDEBUG -fno-strict-aliasing -Werror -D_KERNEL -DKLD_MODULE -nostdinc -I/src -I. -I@ -I@/contrib/altq -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-common -fno-omit-frame-pointer -mcmodel=kernel -mno-red-zone -mfpmath=387 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -msoft-float -fno-asynchronous-unwind-tables -ffreestanding -fstack-protector -std=iso9899:1999 -fstack-protector -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -Wmissing-include-dirs -c nvidia_ctl.c cc1: error: /src: No such file or directory *** Error code 1 At this late hour I can only say that it complies OK for me. Please check your make.conf and env. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: expiration of net/skype ?!
FYI, you're gonna see a nice update in the following days :) -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: expiration of net/skype ?!
On Sun, 1 May 2011 17:31:11 +0100 Chris Rees utis...@gmail.com wrote: On 1 May 2011 08:26, mato gam...@users.sf.net wrote: Chris Rees wrote: Mato wrote: Ok, from my understanding it wouldn't be the first time a port distfile is not (easily) available yet the port itself works if one can get the distfile. And it's very easy to search successfully the interwebs for this particular distfile. In such a case I see no reason to remove the port if it works (under condition one gets the distfile). I myself have it (and I even host it privately). And reading mailing lists reveals there are many people using the port. If one is capable of finding a distfile it's a trivial addition to find the port. Rather than having defective ports in the tree, perhaps you could host the Skype shar? With a decent title it'll probably show up early enough on a Google search. Chris That is one of possibilities. The question is whether we want to lower barriers for new / common users or not. Experience suggests that people will choose a different solution if it makes their life easier. See my other recent post please. Unfortunately, until the port is updated this will not be 'undeprecated'. It is not general policy to allow manual fetches unless a seriously major (ie Java) component requires it. Skype does not fit that mould; there are plenty of viable alternatives. There are other too (all of them annoying for me as a user), and there is not problem with this. But that is the upstream policy about distributing those distfiles -- we don't require users to google and find copies somewhere on the web. I'm not trying to brush you off; I'm just pointing out that the Project will not deliberately breach licensing conditions to make things We don't break them for any reason. easier for new users, neither is there a 'probably broken' part of the Ports tree -- the closest thing to a different repo is a separate tree, for example [1]. Chris [1] http://code.google.com/p/freebsd-texlive/ Anyway, work is underway to fully support newer skype versions, and the biggest part of the work in our linuxulator was done. Again, if you want skype, go on skype's forums and bug them about supporting FreeBSD or at least OSS suport. This being a binary product, there's very little we can realy do when somethign goes wrong. -- Ion-Mihai Tetcu ite...@freebsd.org ___ 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: expiration of net/skype ?!
On Mon, 2 May 2011 12:14:37 +0100 Chris Rees utis...@gmail.com wrote: On 2 May 2011 10:03, Matthias Andree mand...@freebsd.org wrote: Am 02.05.2011 10:49, schrieb Chris Rees: or otherwise issue a hint that the port is kept for the benefit of those who happen to have a distfile. Which is what, thirty people? I don't care. Let's not deliberately break the port for those who can still use it. Please remove the EXPIRATION_DATE; I'm also willing to maintain the port if needed. Although the port is already broken (no-one is deliberately breaking it), there is a possible (temporary) solution for those who want to use their own distfile. ITetcu, miwi, please would you have a look at [1]? It's partly lifted from the diablo ports; just makes it more convenient if one has the distfile already, as well as using IGNORE rather than BROKEN; we know it won't ever build. Chris [1] http://www.bayofrum.net/~crees/patches/skype-distfile.diff Looks good; I was convinced something like this was already committed. -- Ion-Mihai Tetcu ite...@freebsd.org ___ 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: expiration of net/skype ?!
On Tue, 26 Apr 2011 10:29:16 +1000 Peter Jeremy peterjer...@acm.org wrote: On 2011-Apr-26 01:47:30 +0200, martinko gam...@users.sf.net wrote: So what is this deprecation and expiration of net/skype port please ?? Whilst the Skype port still works, the version of Skype referenced by the port is no longer available and later versions of Skype do not (currently) work on FreeBSD. My reading of the Skype license suggests that the FreeBSD Project cannot host the distfile without an agreement with Skype. This means that someone who doesn't currently have the Skype distfile cannot install the Skype port. True, and we've kept it like this for a long time. I have asked people at skype to allow us to redistribute the distfile, but that's impossible for legal reasons (not theirs). I believe work is underway to support the currently available version of Skype. It is, and it's kinda workoing on HEAD plus some patches. One thing all of oyu could do is bug skype on their forums to provide an OSS version; I recently argued about that with their linux product manager, so more voices would help. -- Ion-Mihai Tetcu ite...@freebsd.org ___ 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: Tinderbox question...
On Sat, 2 Apr 2011 09:28:58 +0100 Chris Rees utis...@gmail.com wrote: On 2 April 2011 09:26, Ivan Klymenko fi...@ukr.net wrote: Hi, folks! For example, i built in my tinderbox port audio/clementine-player... It depends on qt4 -* ports... For example, the file qt-everywhere-opensource-src-4.7.2.tar.gz must be downloaded (if not mistaken) for more than five times! Why? File size ~208655K = 5*208655K=1043275K !!! When building ports with these files it is extremely slow and not optimal. As Cris sais, setup DISTFILES caching per README. Is it possible to transfer the function cleandistfiles to another place, that would be cleaning distfiles directory took place after the construction of the entire queue, or do it manually? There isn't done any distfile cleaning as such. For each port build, a chroot is created and populated, then cleaned at the end. For small ports, this takes more that the actual port build; but no, we can't do without it if we are to have an 100% reproducible build env. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: how to bootstrap libtool?
On Wed, 09 Feb 2011 11:40:18 -0800 Chuck Swiger cswi...@mac.com wrote: On Feb 9, 2011, at 11:14 AM, Michael Scheidell wrote: The problem with != is that is is evaluated in a subshell regardless of whether the results are needed, and it happens while the Makefile is first being read, before it tries to figure out which targets need to be processed. Hence this adds a lot of time for each processing, like make index. This is why setting libnet in BUILD_DEPENDS isn't being processed until after these commands are run (or fail to run, as above). which is useless information to me. don't know why, been doing freebsd for 10 years, been a port maintainer for.. ? 4? 5? don't remember. still that is useless information, and doesn't make any sense. doesn't tell me what,why, how, or when to replace what lines with what alternatives. yes, I can hard code it, but I don't really understand what those (inherited lines) actually do. OK. If you don't understand make, and you aren't willing to look at the documentation, then it's hardly surprising that you're having problems figuring things out. Engineers solve problems. Managers create problems. Senior management exists to decide *which* problems management ought to create. (In this particular case, it seems like you ought to delegate the problem to an engineer who has the knowledge to solve it. If I get some free time, I'll see what I can do, otherwise someone else might volunteer) I hope the one that committed the last Makefile version (CC'ed) will have the time to help. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: Skype port renew
On Wed, 9 Feb 2011 21:56:39 +0300 Subbsd sub...@gmail.com wrote: On Tue, Feb 8, 2011 at 10:50 PM, Илья Ермолин ermoli...@gmail.com wrote: Hi, I recently checked out, that on skype official site there is new version of skype for linux. *Skype (beta) 2.1.0.81* Before that to get Skype work I follow some tips from forums about some old version. I tried to download linux static version and run it under freebsd 8.2-RC2 amd64. And it's just work for me (personally I don't use voice or video chat, but ordinary chat works just fine for me...) May be there is time to renew existing port to new version? Unfortunately, some people still use voice) skype-devel port would be useful http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/147549 http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/147550 Hum, so you want the port (-devel) updated for hte new chat/SMS things? That can be done. Voice is a No Go as stated in the audit trail of those PRs. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: Elegant way to update a port
On Wed, 26 Jan 2011 10:32:51 -0600 Paul Schmehl pschmehl_li...@tx.rr.com wrote: A while ago someone posted a url to a website that explained, step by step, how to update a port using cvs and a temporary directory for the updated port. My google foo apparently isn't very good, because I can't seem to find it, and I forgot to bookmark it. Does anyone know what I'm referring to? I really like that way of updating my ports. http://ionut.tetcu.info/FreeBSD//How-to-submit-a-diff.txt Maybe this one? -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: ports/154125: [MAINTAINER] sysutils/lsof: update to 4.85A
On Sun, 23 Jan 2011 23:07:52 -0500
Philip M. Gollucci pgollu...@p6m7g8.com wrote:
On 1/23/2011 10:32 PM, Sunpoet Po-Chuan Hsieh wrote:
Hi,
Before I committed this update, I have tested lsof 4.85A on 8.1 and
it does work fine.
I don't think it is reasonable to remove the patch and prevent 8.1
users from using lsof.
At least, tinderbox running 8.1 requires lsof to work.
hih
fwiw, lsof is optional for tinderbox, the port just happens to list it
unconditionally.
LSOF For killMountProcesses() when using nullfs On \
.if defined(WITH_LSOF)
RUN_DEPENDS+= lsof:${PORTSDIR}/sysutils/lsof
.endif
How's that unconditionally?
--
IOnut - Un^d^dregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B
signature.asc
Description: PGP signature
Re: Elegant way to update a port
On Wed, 26 Jan 2011 12:31:37 -0600
Paul Schmehl pschmehl_li...@tx.rr.com wrote:
--On January 26, 2011 8:18:18 PM +0200 Ion-Mihai Tetcu
ite...@freebsd.org wrote:
On Wed, 26 Jan 2011 10:32:51 -0600
Paul Schmehl pschmehl_li...@tx.rr.com wrote:
A while ago someone posted a url to a website that explained, step
by step, how to update a port using cvs and a temporary directory
for the updated port. My google foo apparently isn't very good,
because I can't seem to find it, and I forgot to bookmark it.
Does anyone know what I'm referring to? I really like that way of
updating my ports.
http://ionut.tetcu.info/FreeBSD//How-to-submit-a-diff.txt
Maybe this one?
Yes! That was it. And thank for the wonderful resource.
Glad to be of service :) It also makes my job as a committer easier.
Back before I was a committer, I was keeping my ports in my CVS, and I
was importing the version in ports a vendor branch with something like
this this scripts are really old, and un-maintained, but may they give
you some ideas) :
#!/bin/sh
##
# $Tecnik: people/itetcu/ports/scripts/imPORT.sh,v 1.11 2008/03/27 12:27:25
itetcu Exp $
#
# $1 should be a module (port)
#
PC=`dirname $0`
echo ${PC}
. ${PC}/PORT.common
echo Checking if you already have $1 in local CVS
cvs -q ${L_CVS_ROOT} co modules || { MERR=Can't co modules merror; }
grep ^$1 modules/modules STATUS=Import || STATUS=Initial import
echo == ${STATUS}
echo Getting $1 from FPT repo
cvs -q ${R_CVS_ROOT} co $1 || { MERR=Can't co port from FPT merror; }
# check for included files
DEPD=$1 expdep
# get category and PORT* and construct CVS-safe string from them
cd $1
CATEGORY=`make -V CATEGORIES | cut -d' ' -f1`
[ -z ${CATEGORY} ] { MERR=Can't get teh CATEGORY; problem in Makefile ?
merror; }
PORTVERSION=`make -V PORTVERSION`
PRT_V_T=`echo ${PORTVERSION} | sed 's/\./_/g`
grep -q '^PORTREVISION' Makefile \
PORTREVISION=`make -V PORTREVISION` PRT_R=__${PORTREVISION}
grep -q '^PORTEPOCH' Makefile \
PORTEPOCH=`make -V PORTEPOCH` PRT_E=,${PORTEPOCH} \
PRT_E_T=-${PORTEPOCH}
CMT_MSG=${STATUS} from FPT of ${CATEGORY}/$1:
$1-${PORTVERSION}${PRT_R}${PRT_E}
REPO=ports/${CATEGORY}/$1
REL_TAG=$1-${PRT_V_T}${PRT_R}${PRT_E_T}
echo ${CMT_MSG}, with tag: ${REL_TAG}
read -p Go on [y/n] ? GOON
if [ x${GOON} = xy ]; then
cvs ${L_CVS_ROOT} import -m ${CMT_MSG} ${REPO} FPT ${REL_TAG} || exit
1
elseexit 1
fi
cd ../
# If doing an initial import we have to add the module and the PRlog
if [ x${STATUS} != xImport ]; then
# add the module and invoke user's editor to sort and ci
echo $1 ${REPO} modules/modules
${EDITOR} modules/modules
cvs -q ${L_CVS_ROOT} ci -m $1 -- ${REPO} modules/modules
cvs release -d modules
# Add PRlog file; for this to work:
# the dir should be like: people/USER/ports/PRlogs/
# and local user should match cvs user
PRlog_DIR=people/`id -un`/ports/PRlogs
cvs -q ${L_CVS_ROOT} co ${PRlog_DIR}
cd ${PRlog_DIR}
touch $1
cvs -q ${L_CVS_ROOT} add $1
cvs -q ${L_CVS_ROOT} ci -m Add PRlog file for $1 $1
cd ../../../../
cvs -q ${L_CVS_ROOT} release -d ${PRlog_DIR}
fi
cd /tmp
rm -r `dirname ${MTMP}`
m tmp/TCVS/people/itetcu/ports/scripts/PORT.common
merror () {
echo ${MERR}
echo Tmp dir: ${MTMP}
exit 1
}
# checks and defaults
[ $# -eq 1 ] || exit 1
#if [ x${HOST} = xit.buh.tecnik93.com ]; then
# L_CVS_ROOT=-d /home/ncvs
#else
export CVS_RSH=ssh
L_CVS_ROOT=-z 9 -d `id -un`@cvs.tecnik93.com:/home/ncvs
#fi
R_CVS_ROOT=-z 9 -d ite...@pcvs.freebsd.org:/home/pcvs/
# our tmp dir
mkdir -p /tmp/CVS/$1/
MTMP=`mktemp -d /tmp/CVS/$1/$1.XXX` || exit 1
#[ -e /tmp/CVS/$1 ] MERR=/tmp/CVS/$1 exists, exiting ... merror
#mkdir -p /tmp/CVS/$1
echo tmp dir: ${MTMP}
cd ${MTMP}
# check to see if this module's Makefile includes something from an other
# if yes export that module also so the relative path is right
expdep () {
pwd
#echo ${DEPD}
DEP_MODS=`egrep '^\.include' ${DEPD}/Makefile | grep -v bsd.port | sed
's,.include ${.CURDIR}/../../,,; s///'`
echo ${DEP_MODS}
if [ -n ${DEP_MODS} ]; then
for dep_mod in ${DEP_MODS}; do
# DEP_MOD_DIR=`echo ${dep_mod} | sed -E 's,/[a-zA-Z0-9_.-]+$,,'`
DEP_MOD_DIR=`dirname ${dep_mod}`
mkdir -p `dirname ${MTMP}`/`dirname ${DEP_MOD_DIR}`
# cvs -q ${L_CVS_ROOT} ex -Dnow -d `dirname ${MTMP}`/`dirname
${dep_mod}` ports/${dep_mod}
_O_PWD=`pwd`
# cd `dirname ${MTMP}`/`dirname ${DEP_MOD_DIR}` \
cd ${MTMP}/${DEP_MOD_DIR} .. \
cvs -q ${L_CVS_ROOT} ex -Dnow -d `basename
${DEP_MOD_DIR}` ports/${dep_mod} || \
(MERR=Could not export ${dep_mod} merror)
cd ${_O_PWD
Re: Updating Claws-Mail
On Mon, 13 Dec 2010 10:31:25 +0100 Alexander Leidinger alexan...@leidinger.net wrote: On Sun, 12 Dec 2010 23:23:51 +0200 Ion-Mihai Tetcu ite...@freebsd.org wrote: On Sun, 12 Dec 2010 21:54:31 +0100 Paweł Pękala c...@o2.pl wrote: docbook2pdf is part of textproc/docbook-utils so now we have all dependencies correctly set. Yes, but we don't want them ;) *Some* people do not want them, so it should be configurable (with the default for at least the official package build cluster to be enabled). Can't we just fetch the file as DSITFILES from somewhere? -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: making all ports in /usr/ports on FreeBSD 8.1
On Mon, 13 Dec 2010 04:30:16 -0800 Rob Farmer rfar...@predatorlabs.net wrote: On Sat, Dec 11, 2010 at 01:29, Norm Larkin norml1...@yahoo.com wrote: Hello, I was idly trying to experiment and decided I wanted to see how long it took, how much disk space was involved, how hard it was on a system, and so on, to build the entire ports tree. I loaded up a fresh system with FreeBSD 8.1R on i386, used all defaults for the installer options, had it install all sources and the ports tree, went into /usr/ports, set BATCH to yes, and did make install. It bombed within about an hour. Figuring my ports were out of date, I repeated this after wiping all of /usr/local, /var/db/pkg, /usr/ports, and then using portsnap to fetch and install. Same result. I then tried loading the amd64 version. Same thing. What am I doing dumb here (other than possibly trying to build all ports). It seems to always get messed up on libxml2. Typescript follows, but I only did a script after it had already failed, so all the intermediate stuff is not there. Script started on Sat Dec 11 02:41:10 2010 freebsd-81r-i386# cd /usr/ports freebsd-81r-i386# setenv BATCH yes freebsd-81r-i386# make install There are a couple problems with this: first, some ports conflict, so you can't have everything installed installed at once. You need to use something like tinderbox to have the builds isolated from one another. Secondly, as you've noticed, the first broken port causes the whole thing to fail. Tinderbox would fix this too. For the last one: make -k -DBATCH -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: Updating Claws-Mail
On Sun, 12 Dec 2010 21:54:31 +0100 Paweł Pękala c...@o2.pl wrote: Dnia 2010-12-11, o godz. 21:26:24 Alexander Leidinger alexan...@leidinger.net napisał(a): Pawel/Martin, yes, I would like to use the --disable-manual part (building the manual by default) to offer the possibility to not have that much dependencies (build depends). Pawel, Claws-Mail 3.7.7 was not building the pdf part of the docs for me. Did it for you? If yes, we have a missing build depends for the manual... There was change in pdf building requirements: 2010-12-03 [paul] 3.7.7cvs11 * configure.ac * manual/xml2pdf ** REMOVED ** * manual/dist/pdf/Makefile.am * manual/es/dist/pdf/Makefile.am * manual/fr/dist/pdf/Makefile.am * manual/pl/dist/pdf/Makefile.am simplify check for tools needed for manual building, remove xml2pdf and use docbook2pdf instead docbook2pdf is part of textproc/docbook-utils so now we have all dependencies correctly set. Yes, but we don't want them ;) -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: INDEX-8 not updated by portsnap?
On Sat, 11 Dec 2010 02:23:56 +0100 (CET) Barbara barbara.xxx1...@libero.it wrote: It seems that starting with the comms/umcs7840 commit, INDEX-8 isn't updated running portsnap. for example: $ ll /usr/ports/sysutils/webmin/Makefile -rw-r--r-- 1 root wheel 3687 Dec 10 18:18 /usr/ports/sysutils/webmin/Makefile $ grep ^PORTVERSION /usr/ports/sysutils/webmin/Makefile PORTVERSION= 1.530 $ grep ^webmin INDEX-8 | cut -d | -f 1 webmin-1.520 I had to get a fresh INDEX-8 running make fetchindex. portsnap6.freebsd.org broke and stopped syncing; it was removed it from the DNS pool a few hours ago. Try again please. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: INDEX-8 not updated by portsnap?
On Sat, 11 Dec 2010 21:38:31 +0100 Matthias Andree mand...@freebsd.org wrote: Am 11.12.2010 21:35, schrieb Barbara: On Sat, 11 Dec 2010 02:23:56 +0100 (CET) Barbara barbara.xxx1...@libero.it wrote: It seems that starting with the comms/umcs7840 commit, INDEX-8 isn't updated running portsnap. for example: $ ll /usr/ports/sysutils/webmin/Makefile -rw-r--r-- 1 root wheel 3687 Dec 10 18:18 /usr/ports/sysutils/webmin/Makefile $ grep ^PORTVERSION /usr/ports/sysutils/webmin/Makefile PORTVERSION= 1.530 $ grep ^webmin INDEX-8 | cut -d | -f 1 webmin-1.520 I had to get a fresh INDEX-8 running make fetchindex. portsnap6.freebsd.org broke and stopped syncing; it was removed it from the DNS pool a few hours ago. Try again please. Now it seems that there are no new snapshots. The last one I got contains sysutils/graid5, which has been committed at 16:50 GMT. INDEX-8 should be 17:35. And now it's 21:33:13 CET, so, if I'm not wrong, about 3 hours have passed since the last snapshot. Same here - and the INDEX files are still out of date: /usr/ports/x11/yeahconsole/ /usr/ports/x11/yelp/ /usr/ports/x11/zenity/ Building new INDEX files... done. [mand...@apollo ~]$ sudo pkg_version -IvL= OpenEXR-1.6.1_3succeeds index (index has 1.6.1_2) libxul-1.9.2.13succeeds index (index has 1.9.2.12) llvm-2.8_2 succeeds index (index has 2.8_1) sqlite3-3.7.4 succeeds index (index has 3.7.3_1) (these are ports I had updated after a make -C /usr/src fetchindex) portsnap builds are currently broken due to portsnap-master being offline this should be fixed soon -- cpecival dixit -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: failed configure of multimedia/handbrake
On Tue, 7 Dec 2010 13:27:02 -0800
Charlie Kester corky1...@comcast.net wrote:
On Tue 07 Dec 2010 at 07:47:41 PST Peter Pentchev wrote:
On Mon, Dec 06, 2010 at 06:27:54PM -0800, Charlie Kester wrote:
I'm getting a strange error while trying to install the handbrake
port:
=== Configuring for handbrake-0.9.3
sed:
/usr/ports/multimedia/handbrake/work/HandBrake-0.9.3//usr/ports/multimedia/handbrake/work/HandBrake-0.9.3/configure:
No such file or directory *** Error code 1
Stop in /usr/ports/multimedia/handbrake.
Looking at the port Makefile and bsd.port.mk, I can't see why sed
is being run here. Nor can I see why ${WRKSRC} is appearing twice
in the path to the configure script.
I'd say lines 110-112 of the Makefile (REINPLACE_CMD on configure)
are why sed is being run :)
Is the post-patch target built *after* the === Configuring...
message is displayed?
No
I saw those lines in the Makefile, and added an ECHO command at the
end of the post-patch commands. It was displayed before ===
Configuring.
yep. the order of the target is enforced in bsd.port.mk
[ .. ]
--
IOnut - Un^d^dregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B
signature.asc
Description: PGP signature
Re: packages compressed with xz
On Fri, 03 Dec 2010 23:07:51 +0200 Volodymyr Kostyrko c.kw...@gmail.com wrote: 30.11.2010 04:40, Julien Laffaye wrote: You can specify limits during compression, so the question is should we do that so that hosts with N MB of RAM can decompress packages? Do we retain the compression ratio over bzip2 if we limit compression memory to 512 MB so that decompression would be possible with, say, 128 MB? According to xz(1), in its default mode (-6), xz uses ~100MiB for compression and ~10MiB for decompression. That seems to be acceptable. You possibly miss something about compression/decompression. The designated memory size is not directly affected only by compression mode. When decompressing you will need memory for: 1. Data history. 2. Dictionary. 3. Some indexes. And those ones are all empty at start. So say, if you are compressing something really huge trying to use 4G of memory you end using that much memory between 2G - 3G of source data. And we will need 512MB to decompress that hunk of data. Are the packages _that_ large? [ .. ] The biggest package that can be produced by a port it's a bit over 10G. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: packages compressed with xz
On Sun, 5 Dec 2010 11:41:29 -0500 Eitan Adler li...@eitanadler.com wrote: Curious - which one? OpenOffice(-3)? He told me on IRC - something in games/ $grep -R NO_PACKAGE /usr/ports/games :-) Hum, looks like either they got smaller or QAT doesn't have all the games packages built yet: -rw-r--r-- 1 root wheel 5.3G Nov 29 02:42 crafty-tablebase-pawn-20070910.tbz -rw-r--r-- 1 root wheel 1.7G Nov 29 01:59 crafty-tablebases-no-pawn-20070910.tbz -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: Introducing USE_SRC and ONLY_FOR_*VER (was: CFR: patch to cleanup usage of SRC_BASE in various ports)
On Fri, 3 Dec 2010 08:59:22 +0100 (CET)
Ganael LAPLANCHE ganael.laplan...@martymac.org wrote:
On Wed, 1 Dec 2010 10:38:10 +0200, Ion-Mihai Tetcu wrote
Hi,
It would be interesting to provide something like :
USE_BASE= yes
Which would do the following :
= defines ${SRC_BASE}
= checks for ${SRC_BASE}/sys/Makefile
= provides a standard error msg if not found
or, if set to something other than yes :
USE_BASE= some/file/within/src_base
= defines ${SRC_BASE}
= check for ${SRC_BASE}/some/file/within/src_base
= provides a standard error msg if not found
Thus, we would avoid having the same tests again and again, and
be able to provide more standard messages...
What do you think ?
Yes. It would help tracking some errors on automated build systems.
Following this idea, here is a small patch that provides that
functionality :
http://people.freebsd.org/~martymac/patches/20101203-patch-bsd.kmod.mk.txt
Submit a PR with it please.
--
IOnut - Un^d^dregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B
signature.asc
Description: PGP signature
Re: CFR: patch to cleanup usage of SRC_BASE in various ports
On Tue, 30 Nov 2010 22:16:17 +0100 (CET)
Ganael LAPLANCHE ganael.laplan...@martymac.org wrote:
On Tue, 30 Nov 2010 14:09:35 -0600, Ade Lovett wrote
Hi Ade, hi Mark !
Patch incorporating these suggestions, along with some other edge
cases I found, uploaded:
http://people.freebsd.org/~linimon/patches/diff.out.srcbase
http://people.FreeBSD.org/~ade/bpm.src_base.diff
Trivial addition to Mk/bsd.port.mk to prevent duplication of
SRC_BASE?= ... in individual port Makefiles.
Good patches, thanks ! But couldn't we extend this idea ?
Most of the time, ${SRC_BASE} is used to check whether some file
(mostly ${SRC_BASE}/sys/Makefile) exists or not, to return,
most of the time, the same error :
you need to extract kernel source tree before building this package
It would be interesting to provide something like :
USE_BASE= yes
Which would do the following :
= defines ${SRC_BASE}
= checks for ${SRC_BASE}/sys/Makefile
= provides a standard error msg if not found
or, if set to something other than yes :
USE_BASE= some/file/within/src_base
= defines ${SRC_BASE}
= check for ${SRC_BASE}/some/file/within/src_base
= provides a standard error msg if not found
Thus, we would avoid having the same tests again and again, and be
able to provide more standard messages...
What do you think ?
Yes. It would help tracking some errors on automated build systems.
--
IOnut - Un^d^dregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B
signature.asc
Description: PGP signature
Re: packages compressed with xz
On Mon, 29 Nov 2010 13:31:10 -0500 jhell jh...@dataix.net wrote: On 11/29/2010 06:24, Matthias Andree wrote: Am 28.11.2010 22:12, schrieb Goran Tal: Now that the base system supports xz compression, it should be used as the default compression for packages. Files compressed with xz are smaller and decompress faster than those compressed with bzip2. This can make an installation much quicker, especially when the complete system is installed or upgraded. Any reasons against it? xz compressed files can take up CONSIDERABLY more memory to decompress than files compressed with bzip2 or gzip. Keep that in mind so that systems that are low on memory can still decompress xz packages. If you don't fit into RAM for decompression, it will be unusable. Adding to this, as the manual says... The decompressing host will need to have at minimal 5% - 20% of memory 'available' for decompression of what the compressing host had. Seeing as FreeBSD still runs on systems with memory as little as 200MB ~20% of 1024MB and quite possible to run on systems with memory of 64MB ~5% of 1024MB I would not see any benefit in modifying the default memory limit on a compressing host to accommodate for these system rather than using gzip(1) or bzip2(1) by default. It would be nice to support xz(1) compression for large selective packages like firefox or openoffice as those will never run on smaller systems. Trouble is it ain't no way (CPU, space, banhdwidth on our side and space,bandwidth on our mirrors side) we could build a double set of packages. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: packages compressed with xz
On Sun, 28 Nov 2010 16:12:48 -0500
Goran Tal goran@gmail.com wrote:
Now that the base system supports xz compression, it should be used as
the default compression for packages.
Files compressed with xz are smaller and decompress faster than those
compressed with bzip2. This can make an installation much quicker,
especially when the complete system is installed or upgraded.
Any reasons against it?
Sigh. We enabled that in HEAD, and after some testing and adapting
{base_OS, ports, tools, etc.} to support that, it will probably become
the default.
One thing against it is the major increase in package time (up to 6x,
but by no means this is a show-stopper).
Resulting packages would be, in medium about 30% smaller (in medium,
for some kinds of data the size is the same as for gzip).
So no, there's no reason against it, just some time is need to adapt
everything.
--
IOnut - Un^d^dregistered ;) FreeBSD user
Intellectual Property is nowhere near as valuable as Intellect
FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B
signature.asc
Description: PGP signature
Re: PR's not being picked up (Was Re: becoming a port committor)
On Mon, 22 Nov 2010 13:19:05 + RW rwmailli...@googlemail.com wrote: On Sun, 21 Nov 2010 23:22:57 -0800 Charlie Kester corky1...@comcast.net wrote: On Sun 21 Nov 2010 at 22:01:28 PST Janky Jay, III wrote: Almost anyone who is an only semi-serious port maintainer (meaning they only have a select few number of ports to maintain and are only trying to contribute/participate) knows that maybe this issue is due to the porter's handbook. Specifically http://www.freebsd.org/doc/en/books/porters-handbook/porting-submitting.html which blatantly states that all submissions whether they are new OR updates be submitted in shar format. Maybe the commiters should bring this up and have a few less to deal with..? Just a suggestion. That page doesn't say what you think it says. Its context is the creation of a new port. It doesn't say anything about updating an existing port. Actually it does discuss the wording of the synopsis for both new and updated ports which gives the impression that that that section covers both. Furthermore the update chapter is at the opposite end of the index under the single misleading word Upgrading. There's no mention of submitting which is what people will be looking for. IMO chapter 10 should either be 3.7 or be merged into 3.6. If anything deserves to be under Quick Porting it's this. Perhaps the problem is that some people never read the *rest* of the handbook? The trouble is that even when people do read handbooks from beginning to end there are always sections that that they are likely to skip until they need them, and this is one of them. Patches with your proposed changes please. Thanks. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: VirtualBox and nullfs
On Fri, 22 Oct 2010 12:42:19 -0700 Cy Schubert cy.schub...@komquats.com wrote: [ .. ] If /usr/local is mounted from a ZFS filesystem, it works. (Not sure about NFS but I suspect it might work too,) [ .. ] Yep.. I run mine with /usr.local being on ZFS. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
New tools for committers and maintainers
Hi, A new tool was just committed to ports, ports-mgmt/distilator. It will check for you each of the MASTER_SITES of the port you call it with. I wold like to recommend that all the maintainers and commiters run it just before submitting/committing. It's fast enough (it doesn't download the DISTFILES, just checks each (MASTER_SITED, DISTFILES) combination and gives you a nice list of what file is (not) where. For speed, you will want to use perl-threaded. And yes, it's on it's way to be integrated into QAT and PortsMon, so there's no reason not to use it yourselves, to prevent receiving those nasty BotMails. A BIG thanks to ehaupt@ for writing it! Have fun, -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: FreeBSD Port: nut-2.4.1_6
On Wed, 13 Oct 2010 14:43:23 +0100 John Bayly john.ba...@tipstrade.net wrote: Hi, I've been working on getting the net port up to the current version (2.4.3), this was before I saw you take ownership of the port. I've currently got it at a stage where I feel it could be added to the ports tree. In addition I've added a bash_completion build option. Is there anything I can do to help out? I started to do the same thing (plus port some GUIs). Send me what you have done, if you want. My time is very low, and I only took the port because it was lately unmaintained and I happen to be using an MGE on my desktop besides the APCs on the serves. If you want to maintain it, I'm happy to give it away :). -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: Install Fuse-SSHFS from ports or from Fuse Website Project ?
On Wed, 22 Sep 2010 15:33:53 +0200 Alexandre axel...@ymail.com wrote: I want to use Fuse-SSHFS http://www.freshports.org/sysutils/fusefs-sshfs/but the port is old (and it got a Sanity Test Failure). When I go to the website of the project Fuse http://sourceforge.net/projects/fuse/ , there is a more recent version fuse-2.8.4.tar.gz and available (?) for FreeBSD. Is anyone is using Fuse-SSHFS and which version : the one from ports or from the project website ? The version in ports froze my system when I tried to save a file opened from the mounted file system. (some 3-4 weeks back), -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: Distributed Version Control for ports(7) ( was: Re: autoconf update )
On Mon, 20 Sep 2010 19:07:17 -0700 per...@pluto.rain.com wrote: Janne Snabb sn...@epipe.com wrote: On Mon, 20 Sep 2010, per...@pluto.rain.com wrote: One issue with either Git or Mercurial is that they are GPL. AFAIK FreeBSD prefers to avoid GPL in the base or in critical widely-used infrastructure if a viable non-GPL alternative exists. The project currently uses Perforce for many sub-projects, so using GPL licenced solution could hardly be a problem. According to the General Information table here: http://en.wikipedia.org/wiki/Comparison_of_revision_control_software Perforce is not GPL -- it is proprietary (but Free ... for OSS development). Thus the fact that FreeBSD currently uses Perforce tells us nothing about the acceptability of a GPL licensed solution. (Ditto for SVN, which -- as someone already pointed out -- is not GPL either.) There are two distributed, BSD-licensed VCS listed on that page: Codeville and Fossil. Both are in ports, but Codeville has been proposed for removal as it seems no longer to be under active development. That leaves Fossil as a possibly-viable BSD-licensed alternative to Mercurial. (Of course, there may be others that aren't listed on that particular Wikipedia page.) Keeping the original recipients when replying (all of them not only To:) would be greatly appreciated (and it's required by the list charted). Thanks, -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: Install Fuse-SSHFS from ports or from Fuse Website Project ?
On Wed, 22 Sep 2010 22:56:27 +0600 Sergey Nikolenko s...@swa.org.ru wrote: On 22.09.2010 22:24, Ion-Mihai Tetcu wrote: I want to use Fuse-SSHFS http://www.freshports.org/sysutils/fusefs-sshfs/but the port is old (and it got a Sanity Test Failure). When I go to the website of the project Fuse http://sourceforge.net/projects/fuse/ , there is a more recent version fuse-2.8.4.tar.gz and available (?) for FreeBSD. Is anyone is using Fuse-SSHFS and which version : the one from ports or from the project website ? The version in ports froze my system when I tried to save a file opened from the mounted file system. (some 3-4 weeks back), Both versions also got this problem: http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/149411 It is something wrong with sysutils/fusefs-kmod on 8.x Hrm .. so is this a general FUSeFS problem? Or just a sshfs one? -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: Distributed Version Control for ports(7) ( was: Re: autoconf update )
On Sun, 19 Sep 2010 02:38:28 -0400 jhell jh...@dataix.net wrote: On 09/18/2010 07:17, Ion-Mihai Tetcu wrote: I'm still to see a concise, clear, precise, listing of advantages that switching from CVS would bring us, that would overcome the effort needed to do it (committers, users, infrastructure, tools). 1). http://bit.ly/d5UrtN 2). http://www.keltia.net/BSDCan/paper.pdf 3). http://bit.ly/97 Y8Xi Make your final comparison here: http://bit.ly/cyQBn8 concise, clear, precise, listing of advantages, that switching from CVS would bring _us_ I have to work daily with 3-4 (D)VCSes for my work and OSS work, so I'm pretty well aware of some good and some bad points of each. 4). Because CVS just does not do any of this. Neither does any of them make coffee or pick up girls for me, but this neither here nor there, since we're talking about advantages - of switching - for ports. General this is why $VCS is the coolest and general features matrix are only the starting point. For the sake of argument can you think of any reason to not switch ? lets hear those, I'm interested. Well, first of all, since we are already using CVS, anyone wishing for a change will have to do the work to break the status quo (ie. convince the rest that is worth the effort). Quick args against: 1. Human side: - all existing committers know to use CVS - we have a few people that know its internals very well - most of the user base also - CVS is simple to use (yes, simple that any of the other; partially because it lacks complicated features) 2. Infrastructure: - everything we have revolves around CVS, from pointy to tindy to portsnap to mirrors to ... 3. All the scripts / apps / ... out there that make use of it or csup. About the only two things I see that we could benefit from switching to something else are: - easy move/rename while preserving history (repocopies now) - better speed for a whole tree checkout/update (if) I've watched the src switch from CVS to SVN, and I can't say it was fully a success. part of the problem is that even after all this time, people haven't completely made the switch in their minds. And the switch implies much more that a table of command equivalencies. Anyone wishing to push for a change will have to: 1. Produce a list of shortcomings of CVS in relation to our ports. 2. Produce a comparison of other VCSes in relation to CVS, CVS' shortcomings in relation to our ports, and each other. 3. Import the existing ports CVS history in the VCS they'd recommend to switch to. 4. Produce a tested migration path (exporter to CVS that works, etc.). 5. Produce a tested migration path for part of the pieces in our infrastructure. 6. Document 4. and 5. and CVS to $VCS user giude and be available to run/fix things related to 4. and 5. for months if not years. 1. to 4. are prerequisites of any serious endeavour to convince our committers and users (and pormgr@, core@). This implies a few month of work, without any guarantee that it won't be for nothing. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: autoconf update
On Fri, 17 Sep 2010 08:12:02 +0200 Dominic Fandrey kamik...@bsdforen.de wrote: On 17/09/2010 06:41, Doug Barton wrote: On 9/16/2010 6:15 PM, Doug Barton wrote: On 9/16/2010 3:35 PM, Anonymous wrote: Dominic Fandreykamik...@bsdforen.de writes: On 16/09/2010 19:17, Dmitry Marakasov wrote: * Dominic Fandrey (kamik...@bsdforen.de) wrote: Just out of curiosity, why a version bump because of a build dependency? I don't think an autoconf update should have an effect on any /running/ software but build systems. And I don't see how rebuilding all the software improves it. This is not a criticism - I just think there is something I don't understand and that worries me. My guess is to uncover *early* build failures that exp-run didn't catch. We shouldn't use our users to beta-test infrastructure changes. Sorry, I'm not feeling well atm and realize that I didn't write what I was thinking here. What I intended to say was that we _don't_ intentionally use the ports system to force our users to beta test changes. I think it goes without saying that we _shouldn't_ do this, although I think that changes like this are a platinum-coated example of why we need to have -stable and -dev branches for ports. I used to disagree with this, because I thought it would create additional work load. Indeed. And the increase it's not linear. I have come to think more favourably of the idea, because you can make more daring commits on a -dev branch and don't have to quick-fix everything that goes wrong. Oh? (Not that I think fixes are being done that quick right now.) You need to do it fast, except for tip ports, because ports depend one on an other. Also the time between a MFC does not have to be very long. A week should be more than enough time to uncover and solve all problems. So the delay to get updates and fixes on the -stable branch is not very long. So you'd need a large userbase running -dev ports and updating very frequently. My2c: let's concentrate on pkg_install for now. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: autoconf update
On Sat, 18 Sep 2010 08:51:39 +0200 Dominic Fandrey kamik...@bsdforen.de wrote: On 18/09/2010 01:13, per...@pluto.rain.com wrote: jhell jh...@dataix.net wrote: ... Mercurial being the distributed version control that it is allows you to clone, make the changes you need to the clone test it thoroughly and then either push or pull them to the main tree ... At the risk of starting the VCS variant of the vi vs emacs wars :) why Mercurial (rather than, say, GIT or SVK)? And no, I have nothing against Mercurial. I don't know _any_ distributed VCS well enough to have an opinion of which would be best suited. There is great documentation and re-education material (for SVN users) out there for Mercurial. I'm sure. But this is not going to happen any way. The ports are still stuck with _CVS_. I'm still to see a concise, clear, precise, listing of advantages that switching from CVS would bring us, that would overcome the effort needed to do it (committers, users, infrastructure, tools). -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: [ports/net/isc-dhcp*] Don't stop DHCP related daemons
On Sun, 12 Sep 2010 06:45:47 +0800 Denny Lin dennyli...@hs.ntnu.edu.tw wrote: On Sat, Sep 11, 2010 at 11:35:43PM +0200, Torfinn Ingolfsen wrote: On Sat, Sep 11, 2010 at 4:33 PM, Ion-Mihai Tetcu ite...@freebsd.org wrote: This 'stop the service before we install' seems to be a new fashion, usually unneeded/disruptive. IMO this should only happen when it's really needed, and with some big warning printed. And perhaps with a restart service attempt afterwards? (maybe interactive as in do you want me to restart the service y/n?) Just my 0.02 euros. How about knobs like WITH_STOP_SERVICE and WITH_START_SERVICE for users who wish to avoid the y/n questions? We have a standard policy of not auto-starting anything. We really don't want a service to be stated automatically after install (think: I installed this today, I'll configure it how I need it tomorrow, then start the service). And you can't really know if it's a new install or an upgrade. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: [ports/net/isc-dhcp*] Don't stop DHCP related daemons
On Sat, 11 Sep 2010 22:29:02 +0900 Norikatsu Shigemura n...@freebsd.org wrote: Hi wxs and jpaetzel. I noticed that dhcpd server stoped after portupgrade, sometimes. It's a painful accident on my network. Because I didn't notice some troubles:-(. Why do you stop the daemons? Is it really absolutely necessary to stop a service before it's files go away? SEE ALSO: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/rc-scripts.html#AEN5402 $ grep forcestop isc-dhcp*/pkg-plist isc-dhcp31-relay/pkg-plist:@unexec %D/etc/rc.d/isc-dhcrelay.sh forcestop 2/dev/null || true isc-dhcp31-relay/pkg-plist:@unexec %D/etc/rc.d/isc-dhcrelay forcestop 2/dev/null || true isc-dhcp31-server/pkg-plist:@unexec %D/etc/rc.d/isc-dhcpd.sh forcestop 2/dev/null || true isc-dhcp31-server/pkg-plist:@unexec %D/etc/rc.d/isc-dhcpd forcestop 2/dev/null || true isc-dhcp41-relay/pkg-plist:@unexec %D/etc/rc.d/isc-dhcrelay.sh forcestop 2/dev/null || true isc-dhcp41-relay/pkg-plist:@unexec %D/etc/rc.d/isc-dhcrelay forcestop 2/dev/null || true isc-dhcp41-server/pkg-plist:@unexec %D/etc/rc.d/isc-dhcpd forcestop 2/dev/null || true I want to remove these lines in pkg-plist. This 'stop the service before we install' seems to be a new fashion, usually unneeded/disruptive. IMO this should only happen when it's really needed, and with some big warning printed. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: New virtual category proposal: enlightenment
On Fri, 10 Sep 2010 09:14:23 +0200 Grzegorz Blach ma...@roorback.net wrote: Hi, I'm working on enlightenment 0.17 ports at: http://dev.roorback.net/enlight-ports and I wanna have this ports in one single category called 'enlightenment', just like afterstep, gnome, kde, windowmaker. Now I have abount 90 ports in tree, and there are next 5 ports from enlightenment 0.16 in FreeBSD ports tree. What do you thing about new category? Submit a patch for adding this as a virtual category. I expect it to be OK'ed. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: Firebird 2.1.x and Firebird 2.5 port
On Sat, 4 Sep 2010 17:01:42 +0300 marius adrian popa map...@gmail.com wrote: Hello i want to takeover the port maintenance for the following ports firebird20-server http://www.freshports.org/databases/firebird20-server and create the new ones for firebird2.1-server firebird2.5-server and update the port for flamerobin Could you help me with the steps that are necessary to be a maintainer of these ports? Submit a PR with your updates, including the maintainership change. See http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html Ping me if you need help. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: ports/148691: [NEW PORT] multimedia/gtk-recordmydesktop
On Sun, 29 Aug 2010 21:45:20 +0200 Rodrigo OSORIO (ros) rodr...@bebik.net wrote: --- Makefile 2010-08-29 21:34:42.0 +0200 +++ Makefile.new 2010-08-29 21:37:11.0 +0200 @@ -2,6 +2,7 @@ # Date created: 16 July 2010 # Whom: Ruslan Mahmatkhanov cvs-...@yandex.ru Please write the date in ISO format -MM-DD. Thanks. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: FreeBSD Port: skype-2.0.0.72,1
On Thu, 29 Jul 2010 13:12:11 -0500 Chad Howsden c...@howsden.net wrote: Hello, I am writing in regards to the skype port for FreeBSD. I currently have the most recent build of FreeNAS running on a newer server box. If you are unaware, FreeNAS is built off of the FreeBSD system. I have successfully installed and configured numerous ports from the freebsd.org site and am currently interested in the skype application. I am wondering if the application is has a command line interface as I don't have an operating system GUI with the FreeNAS server. I am looking to set up a skype server that allows me to free up my personal PC from having the phone connected to it. I plan to use a usb to RJ11 skype adapter with the application to allow me to utilize my phone set I already own. For a more detailed explanation, I plan to do what is done in this article only on my FreeNAS/FreeBSD box instead of a Linux box. Could you provide any insight into whether or not I will be able to accomplish this given the information I have shared with you? I'm a little nervous about frying everything as I have not played around with the skype app yet and am unsure of any glitches or watch-out-fors regarding it. I don't think you can do it with the current skype. However search for the description of skype's API on skype.com. There is some WIP for a partially open-sourced version, that might permit this, but nothing it's out yet. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: dspam install
On Thu, 15 Jul 2010 15:52:45 -0700 (PDT) Doug Barton do...@freebsd.org wrote: On Thu, 15 Jul 2010, David DEMELIER wrote: I'm writing a brand new mail/dspam port from scratch, if I finally finish it in the next fews days I will show you. The only problem I have for now is that there is no WITH_CYRUS_VER like variable so I can't make a per-user defined variable for which cyrus version to install. Sure you can, you just won't have it all handed to you on a silver platter. :) For example, look at how mail/alpine handles the selection of speller. I am away right now, and with very bad abd random net access. I'm afraid anything will have to wait until I get back, at the end of the month. Thanks for your work. -- Ion-Mihai Tetcu io...@tetcu.info ___ 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: dspam install
On Thu, 15 Jul 2010 22:50:32 +0200
David DEMELIER demelier.da...@gmail.com wrote:
2010/7/14 Sahil Tandon sa...@freebsd.org:
[mail/dspam maintainer Cc:'d]
On Tue, 2010-07-13 at 09:46:04 +0200, David DEMELIER wrote:
2010/7/13 Sahil Tandon sa...@freebsd.org:
On Mon, 2010-07-12 at 21:28:56 +0200, David DEMELIER wrote:
.if defined(WITH_MYSQL)
WANT_MYSQL_VER= 55 ...
.endif
Then if the user wants a different version he still can change using :
WITH_MYSQL_VER= 44.
That change by itself will not work because in bsd.database.mk:
.if defined(WITH_MYSQL_VER) ${WITH_MYSQL_VER} != ${WANT_MYSQL_VER}
IGNORE= ...
Then, explain me why do both php5 and php5-pgsql have not
KNOBS/OPTIONS like dspam and work with this variable WITH_PGSQL_VER ?
This is a good opportunity for you to learn about how the ports system
works. Compare the contents of both ports and also review
bsd.database.mk; if, after that, you still do not understand the current
behavior, let us know.
For short, it's like this because it (AFAIR) not all what we have now
in the framework we had back when I worte the port, and because I
wanted to also be able to depend on the server.
--
Ion-Mihai Tetcu io...@tetcu.info
___
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: cvs commit: ports/lang/gprolog Makefile
On Sat, 26 Jun 2010 14:04:36 +0200 Stefan Walter ste...@freebsd.org wrote: Anonymous, 25.06.10, 22:14h CEST: Stefan Walter ste...@freebsd.org writes: Hi, q...@freebsd.org, 25.06.10, 15:08h CEST: The Restless Daemon identified a mtree error while trying to build: gprolog-1.3.1 maintained by po...@freebsd.org Makefile ident: $FreeBSD: ports/lang/gprolog/Makefile,v 1.28 2010/06/25 13:05:33 stefan Exp $ Excerpt from http://QAT.TecNik93.com/logs/8-STABLE-NPD/gprolog-1.3.1.log : I'm unable to reproduce this on a tinderbox. It doesn't leave any files behind there... Even when NOPORTDOCS is defined? Here is a quick fix that makes the port respect NOPORTEXAMPLES, too. Hmm...I didn't see it was set by QAT. Thanks to you and Wesley for the hint and the patch! I just committed it.' From: q...@freebsd.org The build which triggered this BotMail was done under tinderbox-3.3_3; dsversion: 3.2.1 on RELENG_8 on amd64, kern.smp.cpus: 8 with tinderd_flags=-nullfs -plistcheck -onceonly and ccache support, with the official up-to-date Ports Tree, with the following vars set: NOPORTDOCS=yes, NOPORTEXAMPLES=yes, NOPORTDATA=yes, FORCE_PACKAGE=yes. If there is any way to make that more visible, please let me know. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: New pkg-message[.in] guideline idea
On Wed, 23 Jun 2010 18:28:22 +0200 David DEMELIER demelier.da...@gmail.com wrote: Because I always used mv, vim, diff to generate patches I need some time to learn the way to do patches with cvs. http://ionut.tetcu.info/FreeBSD/How-to-submit-a-diff.txt HTH, -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
Re: FreeBSD ports USE_XZ critical issue on low-RAM computers
On Sun, 20 Jun 2010 18:23:03 +0300 Lasse Collin lasse.col...@tukaani.org wrote: On 2010-06-20 Matthias Andree wrote: Am 19.06.2010 15:41, schrieb Lasse Collin: Perhaps FreeBSD provides a good working way to limit the amount of memory that a process actually can use. I don't see such a way e.g. in Linux, so having some method in the application to limit memory usage is definitely nice. It's even more useful in the compression library, because a virtual-memory-hog application on a busy server doesn't necessarily want to use tons of RAM for decompressing data from untrusted sources. Even there the default should be max, and the library SHOULD NOT second-guess what trust level of data the application might to process with libxz's help. There is no default value for the memory limit in liblzma (not libxz, for historical reasons). You can specify UINT64_MAX if you want. Please don't complain how the library sucks without looking at its API first. Don't confuse the limiter _feature_ with its _default value_; there is a default value only in the command line tools. Personally I'd suggest keeping the option to limit the memory, but as an option, not as default. One thing I would really love to see going away is the default to delete the archive on decompression. I really see no reason for it and it makes it very easy to shoot yourself. (And no, I never understood some other compression tools default to deleting the archive file). Expose the limiter interface in the API if you want, but particularly for the library in particular, any other default than unlimited memory is a nuisance. And there's still an application, and unlike the xz library, the application should know what kind of data from what sources it is processing, and if - for instance - a virus inspector wants to impose memory limits and quarantine an attachment with what looks like an zip bomb. Yes, this is exactly what I have done in liblzma, except that there is no default value (typing UINT64_MAX isn't too much to ask). For compression, it's less critical because service is degraded, not denied, but I'd still think -M max would be the better default. I can always put export XZ_OPT=-3 in /etc/profile.d/local.sh or wherever it belongs on the OS of the day. If a script has xz -9, it overrides XZ_OPT=-3. I know. This isn't a surprise for me. The memory limiting however is. And the memory limiting overrides xz -9 to something lesser, which may not be what I want either. I have only one computer with over 512 MiB RAM (this has 8 GiB). Thus xz -9 is usable only on one of my computers. I cannot go and fix all scripts so that they first check how much RAM I have and then pick a reasonable compression level. It doesn't look so good to make xz -9 so low either that it would be usable on all systems with e.g. 256 MiB RAM or more (you can have higher settings than the current xz -9, they just aren't so useful usually, even -9 is not always so useful compared to a bit lower settings). What do you think is the best solution to the above problem without putting a default memory usage limit in xz? Setting something in XZ_OPT might work in many cases, but sometimes scripts set it themselves e.g. to pass compression settings to some other script calling xz. Maybe xz should support a config file? Or maybe another environment variable, which one could assume that scripts won't touch? These are honest questions and answering them would help much more than long descriptions of how the current method is bad. Generally, I think programs should support both, the later overriding the first: .conf - env - command line I still think utilities and applications should /not/ impose arbitrarily lower limits by default though. There's no multithreading in xz yet, but when there is, do you want xz to use as many threads as there are CPU cores _by default_? If so, do you mind if compressing with xz -9 used around 3.5 GiB of memory on a four-core system no matter how much RAM it has? Multithreading in xz is worth discussion if the tasks can be parallelized, which is apparently not the case. You would be duplicating effort, because we have tools to run several xz on distinct files at the same time, for instance BSD portable make or GNU make with a -j option. That's a nice way to avoid answering the question. xargs works too when you have multiple small files (there's even an example on recent man page of xz). Please explain how any of these help with a multigigabyte file. That's where people want xz to use threads. There is more than one way to parallelize the compression, and some of them increase encoder memory usage quite a lot. At the moment, what are the plans and the advantages of multithreding (both on compression and decompression)? I think it is quite obvious that you want the number of threads to be
Re: Unable to update/build security/gpa
On Sun, 20 Jun 2010 12:30:37 -0400 Jason E. Hale bsdkaf...@gmail.com wrote: On Sunday, June 20, 2010 06:55:52 you wrote: FreeBSD-PRERELEASE 8.1 amd64 Since the release of libassuan-2.0.0, I have not been able to update or reinstall security/GPA. All of the other ports appear to build fine. I tried removing the old libassuan-1-1.0.5 ports; however, when attempting to rebuld the 'GPA' port, it only appears to want the older and not newer version of libassuan. Build the newer libassuan port first does not appear to help either. A copy of the last failed build attempt with the newer libassuan port installed follows. Script started on Sun Jun 20 06:44:08 2010 --- Reinstalling 'gpa-0.9.0_5' (security/gpa) --- Building '/usr/ports/security/gpa' === Cleaning for gpa-0.9.0_5 === Vulnerability check disabled, database not found === License check disabled, port has not defined LICENSE === Found saved configuration for gpa-0.9.0_3 === Extracting for gpa-0.9.0_5 = MD5 Checksum OK for gpa-0.9.0.tar.bz2. = SHA256 Checksum OK for gpa-0.9.0.tar.bz2. === Patching for gpa-0.9.0_5 === gpa-0.9.0_5 depends on executable: gpgv2 - found === gpa-0.9.0_5 depends on package: libassuan-1=1.0.5 - not found ===Verifying install for libassuan-1=1.0.5 in /usr/ports/security/libassuan-1 === libassuan-1-1.0.5 conflicts with installed package(s): libassuan-2.0.0 They install files into the same place. Please remove them first with pkg_delete(1). *** Error code 1 Stop in /usr/ports/security/libassuan-1. *** Error code 1 Stop in /usr/ports/security/gpa. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20100620-14986-1cjhi6p-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=gpa-0.9.0_5 UPGRADE_PORT_VER=0.9.0_5 make ** Fix the problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! security/gpa (gpa-0.9.0_5) (unknown build error) Script done on Sun Jun 20 06:44:15 2010 I know all too well. Unfortunately a committer made a hasty move and updated libassuan to version 2.0.0 and then made gnupg 2.x use the newer libassuan. This of course turns into a chain of conflicts because everything else that depends on libassuan 1.x usually needs gnupg 2.x as well. I am working to resolve the situation for my ports, however, the author of gpa has not released a version that will work with libassuan 2.x. There is a ports freeze now too, so I am not sure if my updates will even go through for a while. If you really need to use gpa immediately, I suggest downgrading everything that depended on libassuan 2.x to use libassuan 1.x. Only slush, not full freeze. If your patches fix a problem, they will go in. -- IOnut - Un^d^dregistered ;) FreeBSD user Intellectual Property is nowhere near as valuable as Intellect FreeBSD committer - ite...@freebsd.org, PGP Key ID 057E9F8B493A297B signature.asc Description: PGP signature
