Re: installed ports dependency tree?
Randy Pratt writes: Is there a port that will produce a unified and ordered dependency list, such that upgrading/reinstalling in that order will avoid multiple rebuilds? I though portupgrade could to this, but apparently not. Portupgrade installs several pkg_* tools [1]. The pkg_glob and pkg_sort tools might be what you're looking for. Here's an example: pkg_glob [package names] | pkg_sort pkg_sort seems to be the droid I'm looking for. Thanks. Robert Huff ___ 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: firefox[2,3] will not start after recent ports upgrade
Alexander Konovalenko k...@kth.se 2009-02-01: From: Daniel Roethlisberger dan...@roe.ch ... Could it be the case that firefox-bin hangs in umtxn state? you're right! (Check using ps -laux instead of -aux) http://daemon.nanophys.kth.se/~kono/ktrace_ff2.txt http://daemon.nanophys.kth.se/~kono/ktrace_ff3.txt These trace the wrong process: the wrapper shell script (sh). The actual hanging process would be firefox-bin, not sh. Try ktracing with child processes (-i). ktrace -i showed last line: firefox-bin CALL _umtx_op(0x65f8e0,0x8,0x1,0x65f8c0,0) http://daemon.nanophys.kth.se/~kono/ktrace_ff3_ktrace-i.txt Do you know which port/lib causing this hang on _umtx_op? Unfortunately, no. I have a box with ports tree from around mid-January on which I was unable to fix this problem. Native firefox 2 and 3 hung in umtxn state. So I did pkg_delete -a, rm -rf /usr/local, rebuilt and installed all ports: now the firefox3 build hangs in umtxn state while running a tool called shlibsign. No idea how to fix this. I don't want to update the ports tree to after the unpretty xorg-7.4 changes just yet. I suspect the problem may be related to upgrading using freebsd-update from 7.0 to 7.1, but that's just a wild guess based on the problem appearing after the upgrade; I did make sure no old leftover libraries or binaries were still lying around. -- Daniel Roethlisberger http://daniel.roe.ch/ ___ 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: [Ticket#2009013010000513] FreeBSD Port: rancid-2.3.1_3 / Re: Submit BUG report to FreeBSD for RANCID port with PATCH
The following patches, taken from
'http://blog.glinskiy.com/2007/03/rancid-and-netscreen-firewall.html' address
some
issues with netscreen firewalls.
Please see inline patches below. Thanks!
Your Ticket-Team
Michael Joyner
--
Edward Waters College Information Technology
Tookes Building - 1660 Kings Road, Jacksonville, FL 32209 USA
Email: supp...@otrs.ewc.edu - Web: http://otrs.ewc.edu/otrs/customer.pl
--
Forwarded message from Network Infrastructure Support
netw...@otrs.ewc.edu ---
From:
Network Infrastructure Support netw...@otrs.ewc.edu
To:
it-gr...@listserv.ewc.edu
Subject:
[Ticket#200901301513] Submit BUG report to FreeBSD for RANCID port with
PATCH
Created:
01/30/2009 13:11:56
http://blog.glinskiy.com/2007/03/rancid-and-netscreen-firewall.html
=
[r...@netdisco /usr/local/libexec/rancid]# diff -u -C 5 nlogin.dist nlogin
*** nlogin.dist Fri Jan 30 12:46:12 2009
--- nlogin Fri Jan 30 12:54:43 2009
***
*** 483,500
# Login to the firewall
if {[login $firewall $ruser $userpswd $passwd $enapasswd $prompt $cmethod
$cyphertype]} {
continue
}
! if { $enable } {
! if {[do_enable $enauser $enapasswd]} {
! if { $do_command || $do_script } {
! close; wait
! continue
! }
! }
! }
# we are logged in, now figure out the full prompt
send \r
expect {
-re \[\r\n]+ { exp_continue; }
-re ^.+$prompt { set junk $expect_out(0,string);
--- 483,500
# Login to the firewall
if {[login $firewall $ruser $userpswd $passwd $enapasswd $prompt $cmethod
$cyphertype]} {
continue
}
! # if { $enable } {
! # if {[do_enable $enauser $enapasswd]} {
! # if { $do_command || $do_script } {
! # close; wait
! # continue
! # }
! # }
! #}
# we are logged in, now figure out the full prompt
send \r
expect {
-re \[\r\n]+ { exp_continue; }
-re ^.+$prompt { set junk $expect_out(0,string);
[r...@netdisco /usr/local/libexec/rancid]# diff -u -C 5 nrancid.dist nrancid
*** nrancid.dist Fri Jan 30 12:54:49 2009
--- nrancid Fri Jan 30 12:55:01 2009
***
*** 195,204
--- 195,205
if (/^set admin user (\S+) password (\S+) privilege (\S+)$/
$filter_pwds = 1) {
ProcessHistory(ADMIN,,,
!set admin user $1 password removed privilege $3\n);
next;
+ }
ProcessHistory(,,,$_);
}
$found_end=1;
return(1);
}
Your Ticket-Team
Michael Joyner___
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: [Ticket#2009013010000513] FreeBSD Port: rancid-2.3.1_3 / Re: hrancid PATCH needed
The return codes in hrancid cause problems with at least one model of HP switch
we
have on premises. Please see inlined patch. Thanks!
--
Edward Waters College Information Technology
Tookes Building - 1660 Kings Road, Jacksonville, FL 32209 USA
Email: supp...@otrs.ewc.edu - Web: http://otrs.ewc.edu/otrs/customer.pl
--
*** hrancid.dist Fri Jan 30 14:24:34 2009
--- hrancid Fri Jan 30 14:25:53 2009
***
*** 145,155
while (INPUT) {
tr/\015//d;
last if(/^$prompt/);
next if(/^(\s*|\s*$cmd\s*)$/);
return(-1) if (/command authorization failed/i);
! return(-1) if /^(Invalid|Ambiguous) input:/i;
s/^image//i;
s/^\s*//g;
ProcessHistory(COMMENTS,keysort,C1, ;Image: $_) next;
--- 145,155
while (INPUT) {
tr/\015//d;
last if(/^$prompt/);
next if(/^(\s*|\s*$cmd\s*)$/);
return(-1) if (/command authorization failed/i);
! return(1) if /^(Invalid|Ambiguous) input:/i;
s/^image//i;
s/^\s*//g;
ProcessHistory(COMMENTS,keysort,C1, ;Image: $_) next;
***
*** 184,194
while (INPUT) {
tr/\015//d;
last if (/^$prompt/);
next if (/^(\s*|\s*$cmd\s*)$/);
return(-1) if (/command authorization failed/i);
! return(-1) if /^(Invalid|Ambiguous) input:/i;
/memory\s+-\s+total\s+:\s+(\S+)/i
ProcessHistory(COMMENTS,keysort,B0,;Memory: $1\n);
/serial\s+number\s+:\s+(\S+)/i
ProcessHistory(COMMENTS,keysort,A1,;Serial Number: $1\n);
--- 184,194
while (INPUT) {
tr/\015//d;
last if (/^$prompt/);
next if (/^(\s*|\s*$cmd\s*)$/);
return(-1) if (/command authorization failed/i);
! return(1) if /^(Invalid|Ambiguous) input:/i;
/memory\s+-\s+total\s+:\s+(\S+)/i
ProcessHistory(COMMENTS,keysort,B0,;Memory: $1\n);
/serial\s+number\s+:\s+(\S+)/i
ProcessHistory(COMMENTS,keysort,A1,;Serial Number: $1\n);
***
*** 228,238
while (INPUT) {
tr/\015//d;
last if (/^$prompt/);
next if (/^(\s*|\s*$cmd\s*)$/);
return(-1) if (/command authorization failed/i);
! return(-1) if /^(Invalid|Ambiguous) input:/i;
s/stacking - (Stacking Status).*/$1/i;
s/\s*members unreachable .*$//i;
ProcessHistory(COMMENTS,keysort,F0,;$_);
--- 228,238
while (INPUT) {
tr/\015//d;
last if (/^$prompt/);
next if (/^(\s*|\s*$cmd\s*)$/);
return(-1) if (/command authorization failed/i);
! return(1) if /^(Invalid|Ambiguous) input:/i;
s/stacking - (Stacking Status).*/$1/i;
s/\s*members unreachable .*$//i;
ProcessHistory(COMMENTS,keysort,F0,;$_);
___
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: [Ticket#2009020210000574] FreeBSD Port: rancid-2.3.1_3 / modification to nlogoin patch to fix hang at password prompt / nlogi [...]
Created:
02/02/2009 13:37:50
--- nlogin.dist 2009-01-30 12:46:12.0 -0500
+++ nlogin 2009-02-02 13:33:41.0 -0500
@@ -353,21 +353,12 @@
set uprompt_seen 1
exp_continue
}
- @\[^\r\n]+\[Pp]assword: {
+ password: {
# ssh pwd prompt
sleep 1
send $userpswd\r
exp_continue
}
- \[Pp]assword: {
- sleep 1;
- if {$uprompt_seen == 1} {
- send $userpswd\r
- } else {
- send $passwd\r
- }
- exp_continue
- }
$prompt { break; }
}
}
@@ -485,14 +476,14 @@
if {[login $firewall $ruser $userpswd $passwd $enapasswd $prompt $cmethod
$cyphertype]} {
continue
}
-if { $enable } {
- if {[do_enable $enauser $enapasswd]} {
- if { $do_command || $do_script } {
- close; wait
- continue
- }
- }
-}
+# if { $enable } {
+# if {[do_enable $enauser $enapasswd]} {
+# if { $do_command || $do_script } {
+# close; wait
+# continue
+# }
+# }
+#}
# we are logged in, now figure out the full prompt
send \r
expect {___
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
A plea or sanity in port options menu
I don't believe this is particularly useful: Options for port-fu [ ] BRG Enable BRG support [X] QFZ Enable QFZ support Quite honestly, if you can't figure out that checking the box next to BRG enables BRG support, then don't use a computer. However, if you don't already know what BRG _is_, then those menus are worthless gobbly-gook. So, you've held my hand long enough to teach me that putting an X in a box enables something, but you've given me absolutely NO idea what I've actually done. How about: Options for port-fu [ ] BRG Bernstein Riggs Guillotine parsing [X] QFZ Quantum Freeze Zulu rending At least that one gives me _some_ idea what those TLAs mean. This is so common in the ports infrastructure, that I'm sure a bazillion maintainers are going to scream at me for complaining about it. After all, _everyone_ else does the same thing. But it's completely worthless to have the description simply repeat what the tag is. It's also really bad UI design. Quite honestly, it makes me wonder if the port creator was even awake when they typed up the Makefile. Please, please, please stop this. I'm floored by the pervasiveness of this insanity, and there's absolutely no reason for it to continue. -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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: A plea or sanity in port options menu
On Mon, 2 Feb 2009, Bill Moran wrote: How about: Options for port-fu [ ] BRG Bernstein Riggs Guillotine parsing [X] QFZ Quantum Freeze Zulu rending At least that one gives me _some_ idea what those TLAs mean. There was talk some time ago of having extended descriptions. Several ideas, but the one that made the most sense to me would be a box at the bottom that would display a description as you moved through the options: [.] BRG [X] QFZ Bernstein Riggs Guillotine parsing with the . representing the cursor/highlight position. Move down and the bottom line would change to say Quantum Freeze Zulu rending. The nice thing about the box at the bottom is it would give a full line or possibly several lines for explanations. Seems like it could be added without breaking the existing system with an optional OPTIONS_DESC variable that would correspond with OPTIONS. I don't really know how hard that would be; ideas are cheap, implementation more costly. -Warren Block * Rapid City, South Dakota USA ___ 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: A plea or sanity in port options menu
In response to Warren Block wbl...@wonkity.com: On Mon, 2 Feb 2009, Bill Moran wrote: How about: Options for port-fu [ ] BRG Bernstein Riggs Guillotine parsing [X] QFZ Quantum Freeze Zulu rending At least that one gives me _some_ idea what those TLAs mean. There was talk some time ago of having extended descriptions. Several ideas, but the one that made the most sense to me would be a box at the bottom that would display a description as you moved through the options: [.] BRG [X] QFZ Bernstein Riggs Guillotine parsing with the . representing the cursor/highlight position. Move down and the bottom line would change to say Quantum Freeze Zulu rending. The nice thing about the box at the bottom is it would give a full line or possibly several lines for explanations. Seems like it could be added without breaking the existing system with an optional OPTIONS_DESC variable that would correspond with OPTIONS. I don't really know how hard that would be; ideas are cheap, implementation more costly. I don't think there's any need for any new features in the ports infrastructure. I think it's just a matter of Makefile authors taking the time to describe their options. A quick test of some ports turns up this one: [ ] OPENGL OpenGL support True but useless. How about: [ ] OPENGL Use OpenGL graphics library ...which, at least give the user _some_ idea what they're doing. OpenGL probably isn't a good example, however. It's pretty easy to Google OpenGL and figure out what it is. Here's some more bizarre options: [X] EPUB Epub modules [X] EXTENSIONSExtensions [X] TEMPLATE Templates [X] TOOLS Tools I mean, if I enable Extensions, what happens? How do I figure out what happens? I have to read the Makefile, at which point having these options on a menu is pretty pointless. I mean, I can't even come up with a Google search to help me figure out what tools are involved here. There are some ports that do this very well. For example: [ ] NLS Use internationalized messages [ ] PAM Build with PAM support (server only) [ ] LDAP Build with LDAP authentication support [ ] MIT_KRB5 Build with MIT's kerberos support [ ] HEIMDAL_KRB5 Builds with Heimdal kerberos support [ ] OPTIMIZED_CFLAGS Builds with compiler optimizations (-O3) [X] XML Build with XML data type (server) [X] TZDATAUse internal timezone database (server) [ ] DEBUG Builds with debugging symbols [ ] ICU Use ICU for unicode collation (server) [ ] INTDATE Builds with 64-bit date/time type (server) I mean, a Google on ICU is liable to bring up all sorts of medical drama websites, but I can do a search for ICU unicode and find my answer on the first result. Not only am I told that optimized compiler flags are an option, but I'm told the exact one that will be used (-O3) The porters handbook doesn't seem to offer any helpful advice on these: http://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.html In fact, the examples it provides are excellent examples of doing it WRONG. Let me see about making a patch to the porters handbook to provide some advice ... -- Bill Moran http://www.potentialtech.com http://people.collaborativefusion.com/~wmoran/ ___ 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
Current unassigned ports problem reports
(Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description o ports/131289X11 xorg 7.4 exiting the server leads to instantaneous f ports/131288[PATCH] security/prelude-manager: update to 0.9.14.2 f ports/131287[PATCH] security/prelude-lml: update to 0.9.14 f ports/131286[PATCH] security/libprelude: update to 0.9.21.2 o ports/131276[NEW PORT] xf86-video-nouveau o ports/131269New port: net/cclive Lightweight cmdline video extrac f ports/131268[patch] - update mail/dcc-dccd to version 1.3.102 o ports/131256[Update + fix] emulators/cpmtools27: Update to 2.8 o ports/131252Update irc/ircii-20060725_1 to irc/ircii-20080314 o ports/131233multimedia/mplayer: gmplayer stopped working o ports/131230[NEW PORT] games/linux-coldwar-demo: Coldwar Demo - a o ports/131227Update net/empty 0.6.15b to net/empty 0.6.16b o ports/131226Update net/rtpbreak 1.3 to rtpbreak 1.3a o ports/131223[maintainer update] devel/dyncall o ports/131218www/privoxy+ipv6: /etc/rc: WARNING: run_rc_command: ca f ports/131204audio/musicpd: fix aac decoding o ports/131194[NEW PORT] games/linux-ningpo-demo: NingPo Mahjong Dem o ports/131191[NEW PORT] games/linux-candycruncher-demo: Candy Crunc o ports/131187[NEW PORT] games/linux-majesty-demo: Majesty Gold Demo o ports/131181[patch] - update sysutils/rsyslog4 to version 4.1.4 o ports/131169New port lang/ikarus: optimizing incremental Scheme co o ports/131168new port: devel/lpc21isp o ports/131166[NEW PORT] net-mgmt/p5-NetApp: Perl interface to manag o ports/131165[NEW PORT] devel/p5-Data-Dumper-Perltidy: Stringify an o ports/131161Syntax error in mail/dkim-milter start script o ports/131155[NEW PORT] devel/p5-Config-IniRegEx: Ini workaround, r o ports/131148[NEW PORT] net/p5-Amazon-EC2: Perl Library for Amazon f ports/131109net/jicmp upgrade from v1.0.8 to 1.0.9 f ports/131093chrooting net/isc-dhcp30-server to aliased /home can c f ports/131049Port www/firefox-remote still uses X11BASE variable o ports/131041[new port] x11-themes/gtk-nodoka-engine: GTK nodoka en f ports/130972sysutils/gnomebaker 0.6.4 dumps core when trying to cr f ports/130966multimedia/mplayer: gmplayer cannot start o ports/130925New port: x11-toolkits/soqt4 - Qt4 toolkit library f ports/130898www/mediawiki fails to identify diff3 f ports/130828graphics/xnview can not work in the FreeBSD 7.1 f ports/130779[PATCH] emulators/dosbox enable directserial passthrou f ports/130760science/netcdf: link problem with fortran library f ports/1307417.1-RELEASE/ports/sysutils/coreutils/Makefile add BUIL o ports/130719www/nspluginwrapper installs plugins in the old direct o ports/130715New Port:devel/binutils-2.19 o ports/130647devel/p5-File-Pid: uninitialized value warning if you f ports/130633www/c-icap: update to 060708 o ports/130541new port: net/isc-dhcp41-server f ports/130326[patch] update to sysutils/megarc f ports/130314[Update]graphics/gpicview:update to 0.1.11 f ports/130209www/typo3 upgrade removes configuration f ports/130202[PATCH] net-im/pidgin-guifications: update to 2.16 f ports/130065devel/stlport update to 5.2.1 and problems f ports/130063databases/rrdtool update f ports/130047update cad/ngspice_rework to version 18 f ports/129977[UPDATE] net/acx100 to latest (working?) version o ports/129677/usr/ports/sysutils/aaccli Bad system call: 12 (core d o ports/129606benchmarks/iozone does not support O_DIRECT o ports/129598Update ports: finance/aqbanking, devel/gwenhywfar to 3 o ports/129478multimedia/acidrip: patch file to commit to ports f ports/129435java/jakarta-commons-dbcp not BROKEN on jdk15 o ports/129363devel/ace build fails if kernel module aio is loaded o ports/128603textproc/flex has too small capacity f ports/128490net/freenx port does not work properly on freebsd-7 st f ports/128271biology/ncbi-toolkit - blastall segfaults when output o ports/128140update devel/pwlib to 2.4.1 to fit GNOME 2.24 o ports/127851
Re: A plea or sanity in port options menu
On Monday 02 February 2009 6:39:25 pm Bill Moran wrote: In response to Warren Block wbl...@wonkity.com: On Mon, 2 Feb 2009, Bill Moran wrote: How about: Options for port-fu [ ] BRG Bernstein Riggs Guillotine parsing [X] QFZ Quantum Freeze Zulu rending At least that one gives me _some_ idea what those TLAs mean. There was talk some time ago of having extended descriptions. Several ideas, but the one that made the most sense to me would be a box at the bottom that would display a description as you moved through the options: [.] BRG [X] QFZ Bernstein Riggs Guillotine parsing with the . representing the cursor/highlight position. Move down and the bottom line would change to say Quantum Freeze Zulu rending. The nice thing about the box at the bottom is it would give a full line or possibly several lines for explanations. Seems like it could be added without breaking the existing system with an optional OPTIONS_DESC variable that would correspond with OPTIONS. I don't really know how hard that would be; ideas are cheap, implementation more costly. I don't think there's any need for any new features in the ports infrastructure. I think it's just a matter of Makefile authors taking the time to describe their options. A quick test of some ports turns up this one: [ ] OPENGL OpenGL support True but useless. How about: [ ] OPENGL Use OpenGL graphics library ...which, at least give the user _some_ idea what they're doing. OpenGL probably isn't a good example, however. It's pretty easy to Google OpenGL and figure out what it is. Here's some more bizarre options: [X] EPUB Epub modules [X] EXTENSIONSExtensions [X] TEMPLATE Templates [X] TOOLS Tools I mean, if I enable Extensions, what happens? How do I figure out what happens? I have to read the Makefile, at which point having these options on a menu is pretty pointless. I mean, I can't even come up with a Google search to help me figure out what tools are involved here. There are some ports that do this very well. For example: [ ] NLS Use internationalized messages [ ] PAM Build with PAM support (server only) [ ] LDAP Build with LDAP authentication support [ ] MIT_KRB5 Build with MIT's kerberos support [ ] HEIMDAL_KRB5 Builds with Heimdal kerberos support [ ] OPTIMIZED_CFLAGS Builds with compiler optimizations (-O3) [X] XML Build with XML data type (server) [X] TZDATAUse internal timezone database (server) [ ] DEBUG Builds with debugging symbols [ ] ICU Use ICU for unicode collation (server) [ ] INTDATE Builds with 64-bit date/time type (server) I mean, a Google on ICU is liable to bring up all sorts of medical drama websites, but I can do a search for ICU unicode and find my answer on the first result. Not only am I told that optimized compiler flags are an option, but I'm told the exact one that will be used (-O3) The porters handbook doesn't seem to offer any helpful advice on these: http://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.html In fact, the examples it provides are excellent examples of doing it WRONG. Let me see about making a patch to the porters handbook to provide some advice ... +1,000,000 on your idea. Yes .. you are absolutely right ... even if you know your way around make gcc compiling software .. and even if you _really_ know your way around make gcc compiling software, there's no chance on earth that anyone can tell what does every single option on every single Makefile actually mean. As you pointed out: [ ] BRG [X] QFZ means _nothing_ to 99.9% of the users... Be Really Grumpy? Buy Red Goggles? Quite Faster Zapping?? Quit Filtering Zealots?? This kind of things really hurts the good documentation reputation that FreeBSD has rightfully earned. And I do agree with you: I don't think there's any need for any new features in the ports infrastructure. I think it's just a matter of Makefile authors taking the time to describe their options. And once again .. this is the way to go for me too: There are some ports that do this very well. For example: [ ] NLS Use internationalized messages [ ] PAM Build with PAM support (server only) [ ] LDAP Build with LDAP authentication support [ ] MIT_KRB5 Build with MIT's kerberos support [ ] HEIMDAL_KRB5 Builds with Heimdal kerberos support [ ] OPTIMIZED_CFLAGS Builds with compiler optimizations (-O3) [X] XML Build with XML data type (server) [X] TZDATAUse internal timezone database (server) [ ] DEBUG Builds with debugging symbols [ ] ICU Use ICU for unicode collation (server) [ ] INTDATE Builds with 64-bit date/time type (server)
Re: how remove old lib in portupgrade -fr libxcb
On Mon, 2009-02-02 at 06:46 -0500, Jerry wrote: On Sun, 01 Feb 2009 21:02:17 +0100 Sebastien Chassot si...@fsfe.org wrote: I did another try portupgrade -frP libxcb I believe the 'P' options is causing the problem. Update your ports tree and run it with that option; i.e., portupgrade -fr libxcb as shown in UPDATING. I think your probably right. I'm not use with port/package and I don't know how it works. Package maybe don't rebuild link same way make does (?) As ports are long to build I hoped save some time...silly me ;) I'll try without P... Sebastien ___ 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: [kde-freebsd] Call for Testing KDE 4.2 for FreeBSD
On February 1, 2009 11:03 pm David Johnson wrote: The KDE FreeBSD team is happy to announce the first public Call for Testing for KDE 4.2. Over the past weeks we have focused on the complex and very time consuming task to get KDE 4.2 running. Here are some random notes of mine. Some are tips, some are problems, some are just observations. * I am getting the vista-effect as my older 2.8Gz P4 / Radeon 9000 aren't up to the task of KDE4. I have desktop effects turned off. I've heard some rumours that Qt 4.5 may improve things, but I really do need to get a new computer. The days of refurbishing older hardware by installing *Nix may be drawing to an end... You definitely should not be getting a vista-effect with that hardware. I also have a P4 2.8 GHz CPU, but with crappy onboard Intel i915 graphics (8 MB shared RAM), and 2 GB of RAM; and I don't have any noticeable slowdown in the GUI. The only time things are slow is when I try to load multiple apps at once, and the harddrive grinds away. Once apps are loaded, things are smooth and quick, and the desktop is always smooth and quick. I even ran with desktop effects on with KDE 4.1 for a couple of weeks, but there were visual glitches with the Intel graphics. * All my KDE3 apps are showing up in my menus. I've even set XDG_DATA_DIRS, to no effect. Does anyone know of an easy way to segregate them out into their own menu? That's because there's only 1 application launcher menu, for all your installed apps, whether they be KDE3, KDE4, GNOME, XFce, X11, etc. If you don't want an app to show in the menu, you either have to manually edit the menu, or uninstall the app. What you're asking for is like running Windows Vista, but having all your Windows XP and Win98 apps show up in a separate menus. * The main menu is very slow, whether it's kickoff or classic. Opening up a submenu may take ten to fifteen seconds, with some noticeable disk activity. Very annoying. That's not right. Something strange is going on, but not sure where to even begin diagnosing something like that. -- Freddie fjwc...@gmail.com ___ 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
committer please update cfengine ports?
I'm the maintainer for the cfengine port, and I've got two updates which need to be committed. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/131040 Updates cfengine port to 2.2.9. My tested revision is showing there right now, but it should be as soon as the followup posts my reply to that thread. http://www.freebsd.org/cgi/query-pr.cgi?pr=131311 This is a new port for cfengine v3. -- Jo Rhett Net Consonance : consonant endings by net philanthropy, open source and other randomness ___ 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
package server inconsistencies
A friend and me are both working on tools for automated package updates. We intended to rely on the INDEX file to be found on the package repositories, however we came to recognize that the data provided is not reliable. Here's an example: ftp://ftp.de.freebsd.org/pub/FreeBSD/ports/amd64/packages-7-stable/INDEX Yesterday the OOo-3 version listed was openoffice.org-3.0.0 However under ftp://ftp.de.freebsd.org/pub/FreeBSD/ports/amd64/packages-7-stable/All you already found openoffice.org-3.0.0_1 editors/openoffice.org-3.0.0.tbz was a broken link at that time. Today this has returned to a consistent state, however yesterday relying on INDEX would have been fatal. Our code would have attempted to update with the wrong version and gracelessly failed. Was this some kind of exception or do we have to add server/INDEX consistency tests to our algorithms? Shouldn't old packages be kept until they are no longer referenced by the INDEX? ___ 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: firefox[2,3] will not start after recent ports upgrade
Garrett Cooper yanef...@gmail.com 2009-02-02:
On Mon, Feb 2, 2009 at 8:38 AM, Daniel Roethlisberger dan...@roe.ch wrote:
Alexander Konovalenko k...@kth.se 2009-02-01:
From: Daniel Roethlisberger dan...@roe.ch
...
Could it be the case that firefox-bin hangs in umtxn state?
you're right!
(Check using ps -laux instead of -aux)
http://daemon.nanophys.kth.se/~kono/ktrace_ff2.txt
http://daemon.nanophys.kth.se/~kono/ktrace_ff3.txt
These trace the wrong process: the wrapper shell script (sh).
The actual hanging process would be firefox-bin, not sh. Try
ktracing with child processes (-i).
ktrace -i showed last line:
firefox-bin CALL _umtx_op(0x65f8e0,0x8,0x1,0x65f8c0,0)
http://daemon.nanophys.kth.se/~kono/ktrace_ff3_ktrace-i.txt
Do you know which port/lib causing this hang on _umtx_op?
Unfortunately, no. I have a box with ports tree from around
mid-January on which I was unable to fix this problem. Native
firefox 2 and 3 hung in umtxn state. So I did pkg_delete -a, rm
-rf /usr/local, rebuilt and installed all ports: now the firefox3
build hangs in umtxn state while running a tool called shlibsign.
No idea how to fix this. I don't want to update the ports tree
to after the unpretty xorg-7.4 changes just yet.
I suspect the problem may be related to upgrading using
freebsd-update from 7.0 to 7.1, but that's just a wild guess
based on the problem appearing after the upgrade; I did make sure
no old leftover libraries or binaries were still lying around.
Have you read UPDATING yet about the libxcb upgrade?
Cheers,
-Garrett
$ fgrep xcb /usr/{ports,src}/UPDATING | wc -l
0
Note that this is a non-current ports tree from before the xorg
7.4 update (mid-January), which used to work fine in the exact
same configuration on RELENG_7_0, but broke on RELENG_7_1. This
is using the version of libxcb committed by miwi in September
2008. The libxcb shlib version bump really cannot be related to
this unless I am very much mistaken.
--
Daniel Roethlisberger
http://daniel.roe.ch/
___
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: installed ports dependency tree?
On Sun, 1 Feb 2009 22:48:37 -0500 Robert Huff roberth...@rcn.com wrote: Suppose I have installed ports A..Z. Some of these are standakone; some depend on others on the list; others depend on installed ports not on the list. Is there a port that will produce a unified and ordered dependency list, such that upgrading/reinstalling in that order will avoid multiple rebuilds? I though portupgrade could to this, but apparently not. Portupgrade installs several pkg_* tools [1]. The pkg_glob and pkg_sort tools might be what you're looking for. Here's an example: pkg_glob [package names] | pkg_sort This produces a list for update order. The man pages are quite helpful for the pkg_* tools. HTH, Randy [1] Run pkg_info -L portupgrade-\* to see the complete packing list for portupgrade. ___ 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
Earn real money
Dear I invite you to the must powerful opportunity of 2009 simple visit one of those link www.louisdavidoff.myworldresults.com/ http://louisdavidoff.myworldpower.com/ http://louisdavidoff.onelinebuilder.com/ http://louisdavidoff.myworldmoms.com/ thank you! Unsubscribe from Email List To be removed from from MyWorldPlus system, please verify that the email address below is your full email address: http://www.myworldplus.com/away?id=3160074email=louisdavid...@gmail.com ___ 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: how remove old lib in portupgrade -fr libxcb
On Sun, 01 Feb 2009 21:02:17 +0100 Sebastien Chassot si...@fsfe.org wrote: I did another try portupgrade -frP libxcb I believe the 'P' options is causing the problem. Update your ports tree and run it with that option; i.e., portupgrade -fr libxcb as shown in UPDATING. -- Jerry ges...@yahoo.com Fame may be fleeting but obscurity is forever. signature.asc Description: PGP signature
FreeBSD Port: ejabberd-1.1.4_2
Hello, Shaun. Please update your port ejabber, the current version is outdated. The last actual version 2.0.3 (http://www.process-one.net/en/ejabberd/downloads) I am sorry for the spelling, I do not know English. -- С уважением, Aleksandr mailto:aleksandr-kobyche...@ya.ru ___ 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: firefox[2,3] will not start after recent ports upgrade
On Mon, Feb 2, 2009 at 8:38 AM, Daniel Roethlisberger dan...@roe.ch wrote: Alexander Konovalenko k...@kth.se 2009-02-01: From: Daniel Roethlisberger dan...@roe.ch ... Could it be the case that firefox-bin hangs in umtxn state? you're right! (Check using ps -laux instead of -aux) http://daemon.nanophys.kth.se/~kono/ktrace_ff2.txt http://daemon.nanophys.kth.se/~kono/ktrace_ff3.txt These trace the wrong process: the wrapper shell script (sh). The actual hanging process would be firefox-bin, not sh. Try ktracing with child processes (-i). ktrace -i showed last line: firefox-bin CALL _umtx_op(0x65f8e0,0x8,0x1,0x65f8c0,0) http://daemon.nanophys.kth.se/~kono/ktrace_ff3_ktrace-i.txt Do you know which port/lib causing this hang on _umtx_op? Unfortunately, no. I have a box with ports tree from around mid-January on which I was unable to fix this problem. Native firefox 2 and 3 hung in umtxn state. So I did pkg_delete -a, rm -rf /usr/local, rebuilt and installed all ports: now the firefox3 build hangs in umtxn state while running a tool called shlibsign. No idea how to fix this. I don't want to update the ports tree to after the unpretty xorg-7.4 changes just yet. I suspect the problem may be related to upgrading using freebsd-update from 7.0 to 7.1, but that's just a wild guess based on the problem appearing after the upgrade; I did make sure no old leftover libraries or binaries were still lying around. Have you read UPDATING yet about the libxcb upgrade? Cheers, -Garrett ___ 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: [kde-freebsd] Call for Testing KDE 4.2 for FreeBSD
On Sunday 01 February 2009 23:02:28 Martin Wilke wrote: Howdy Guys, The KDE FreeBSD team is happy to announce the first public Call for Testing for KDE 4.2. Over the past weeks we have focused on the complex and very time consuming task to get KDE 4.2 running. Please read UPDATING-area51 before you start your update. To get KDE 4.2: try svn co https://kf.athame.co.uk/kde-freebsd/trunk/area51/ /path/to/area51 More info here: https://kf.athame.co.uk/access.php - Martin (on behalf of the KDE FreeBSD team) Hi, I'll get started on testing today. I however have this strange desire to use USB2 (the new USB stack introduced to FreeBSD-Current). Is KDE4 happy with USB2 (or to be more precise, is hald happy with USB2 yet)? Is there anything special required to compile KDE4 (and all other ports) to support USB2? I assume installing with KERNCONF=USB2 is a requirement :-) Thanks for the great work, much appreciated. Regards, David signature.asc Description: This is a digitally signed message part.
Re: [kde-freebsd] Call for Testing KDE 4.2 for FreeBSD
On Sunday 01 February 2009 21:02:28 Martin Wilke wrote: Howdy Guys, The KDE FreeBSD team is happy to announce the first public Call for Testing for KDE 4.2. Over the past weeks we have focused on the complex and very time consuming task to get KDE 4.2 running. What is new: Where KDE 4.1 was, according to the development team, aimed at casual users, KDE 4.2 is billed as a compelling offering for the majority of end users. There have been further enhancements to the plasma desktop with new applets allowing better desktop customisation. The configuration options for the desktop have also been expanded and the revamped system tray shows reports from every conceivable process, from system messages to the status of large downloads. The KWin window manager has learned a couple of new tricks. By default, it now switches on 3D and compositing effects automatically, on suitable hardware and manages these effects autonomously, without the aid of Compiz. With the help of the new Kephal library, the window manager now offers additional options for running multiple monitors. The Dolphin file manager has been partly revised, and should now be easier to use. As part of the Google Summer of Code, KMail has been redesigned, resulting in both a better appearance and better IMAP support. The KDE browser Konqueror also includes several new features. New supported languages include Arabic, Icelandic, Basque, Hebrew, Romanian, Tajik and several Indian languages (Bengali India, Gujarati, Kannada, Maithili, Marathi) indicating a rise in popularity in this part of Asia. Some note: The CFT is now without FreeBSD 6.4 support. We will see what we can do over the week now but I do not promise that we can get this fixed. If you want to help us, your patches are welcome. We suggest that you exit from KDE4 before you update, backup your ~/.kde4 configuration dir and start with a clean config. New Ports: arabic/kde4 l10n misc/kde4-l10n-eu hebrew/kde4-l10n misc/kde4-l10n-is misc/kde4-l10n-ro misc/kde4-l10n-tg Please read UPDATING-area51 before you start your update. To get KDE 4.2: try svn co https://kf.athame.co.uk/kde-freebsd/trunk/area51/ /path/to/area51 More info here: https://kf.athame.co.uk/access.php Here few screenshots: http://miwi.bsdcrew.de/screens/kde42/ I'd like to say thanks to all helpers and submitters on the kde-freebsd@ mailinglist. That's all for the moment. Happy Testing! - Martin (on behalf of the KDE FreeBSD team) Awesome, as far as I can see :-) My plasmoids and kicker are back working on my nv-based system, propably not an improvement of kde4.2 but a result of wiping all ports when xorg upgrade to 7.4 failed. Overall speed has improved due to one of those actions. juk is picky now concerning 's and umlauts in filenames, therefore it doesn't skip tracks anymore with raising info (error) windows. ___ 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: A plea or sanity in port options menu
Gonzalo Nemmi wrote: On Monday 02 February 2009 6:39:25 pm Bill Moran wrote: In response to Warren Block wbl...@wonkity.com: On Mon, 2 Feb 2009, Bill Moran wrote: How about: Options for port-fu [ ] BRG Bernstein Riggs Guillotine parsing [X] QFZ Quantum Freeze Zulu rending At least that one gives me _some_ idea what those TLAs mean. There was talk some time ago of having extended descriptions. Several ideas, but the one that made the most sense to me would be a box at the bottom that would display a description as you moved through the options: [.] BRG [X] QFZ Bernstein Riggs Guillotine parsing with the . representing the cursor/highlight position. Move down and the bottom line would change to say Quantum Freeze Zulu rending. The nice thing about the box at the bottom is it would give a full line or possibly several lines for explanations. Seems like it could be added without breaking the existing system with an optional OPTIONS_DESC variable that would correspond with OPTIONS. I don't really know how hard that would be; ideas are cheap, implementation more costly. I don't think there's any need for any new features in the ports infrastructure. I think it's just a matter of Makefile authors taking the time to describe their options. A quick test of some ports turns up this one: [ ] OPENGL OpenGL support True but useless. How about: [ ] OPENGL Use OpenGL graphics library ...which, at least give the user _some_ idea what they're doing. OpenGL probably isn't a good example, however. It's pretty easy to Google OpenGL and figure out what it is. Here's some more bizarre options: [X] EPUB Epub modules [X] EXTENSIONSExtensions [X] TEMPLATE Templates [X] TOOLS Tools I mean, if I enable Extensions, what happens? How do I figure out what happens? I have to read the Makefile, at which point having these options on a menu is pretty pointless. I mean, I can't even come up with a Google search to help me figure out what tools are involved here. There are some ports that do this very well. For example: [ ] NLS Use internationalized messages [ ] PAM Build with PAM support (server only) [ ] LDAP Build with LDAP authentication support [ ] MIT_KRB5 Build with MIT's kerberos support [ ] HEIMDAL_KRB5 Builds with Heimdal kerberos support [ ] OPTIMIZED_CFLAGS Builds with compiler optimizations (-O3) [X] XML Build with XML data type (server) [X] TZDATAUse internal timezone database (server) [ ] DEBUG Builds with debugging symbols [ ] ICU Use ICU for unicode collation (server) [ ] INTDATE Builds with 64-bit date/time type (server) I mean, a Google on ICU is liable to bring up all sorts of medical drama websites, but I can do a search for ICU unicode and find my answer on the first result. Not only am I told that optimized compiler flags are an option, but I'm told the exact one that will be used (-O3) The porters handbook doesn't seem to offer any helpful advice on these: http://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.html In fact, the examples it provides are excellent examples of doing it WRONG. Let me see about making a patch to the porters handbook to provide some advice ... +1,000,000 on your idea. Yes .. you are absolutely right ... even if you know your way around make gcc compiling software .. and even if you _really_ know your way around make gcc compiling software, there's no chance on earth that anyone can tell what does every single option on every single Makefile actually mean. As you pointed out: [ ] BRG [X] QFZ means _nothing_ to 99.9% of the users... Be Really Grumpy? Buy Red Goggles? Quite Faster Zapping?? Quit Filtering Zealots?? This kind of things really hurts the good documentation reputation that FreeBSD has rightfully earned. And I do agree with you: I don't think there's any need for any new features in the ports infrastructure. I think it's just a matter of Makefile authors taking the time to describe their options. And once again .. this is the way to go for me too: There are some ports that do this very well. For example: [ ] NLS Use internationalized messages [ ] PAM Build with PAM support (server only) [ ] LDAP Build with LDAP authentication support [ ] MIT_KRB5 Build with MIT's kerberos support [ ] HEIMDAL_KRB5 Builds with Heimdal kerberos support [ ] OPTIMIZED_CFLAGS Builds with compiler optimizations (-O3) [X] XML Build with XML data type (server) [X] TZDATAUse internal timezone database (server) [ ] DEBUG Builds with debugging symbols [ ] ICU Use ICU for unicode collation (server) [ ] INTDATE Builds with 64-bit date/time
FreeBSD Port: rancid-devel-2.3.2a7_1
Hi, Do you have any near-term plans to bring rancid-devel up to 2.3.2a9? There are some specific clogin improvements I'd like to move to, but can just one-off that particular script for now if necessary. dp ___ 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: A plea or sanity in port options menu
On Monday 02 February 2009 10:29:16 pm Eitan Adler wrote: Gonzalo Nemmi wrote: On Monday 02 February 2009 6:39:25 pm Bill Moran wrote: In response to Warren Block wbl...@wonkity.com: On Mon, 2 Feb 2009, Bill Moran wrote: How about: Options for port-fu [ ] BRG Bernstein Riggs Guillotine parsing [X] QFZ Quantum Freeze Zulu rending At least that one gives me _some_ idea what those TLAs mean. There was talk some time ago of having extended descriptions. Several ideas, but the one that made the most sense to me would be a box at the bottom that would display a description as you moved through the options: [.] BRG [X] QFZ Bernstein Riggs Guillotine parsing with the . representing the cursor/highlight position. Move down and the bottom line would change to say Quantum Freeze Zulu rending. The nice thing about the box at the bottom is it would give a full line or possibly several lines for explanations. Seems like it could be added without breaking the existing system with an optional OPTIONS_DESC variable that would correspond with OPTIONS. I don't really know how hard that would be; ideas are cheap, implementation more costly. I don't think there's any need for any new features in the ports infrastructure. I think it's just a matter of Makefile authors taking the time to describe their options. A quick test of some ports turns up this one: [ ] OPENGL OpenGL support True but useless. How about: [ ] OPENGL Use OpenGL graphics library ...which, at least give the user _some_ idea what they're doing. OpenGL probably isn't a good example, however. It's pretty easy to Google OpenGL and figure out what it is. Here's some more bizarre options: [X] EPUB Epub modules [X] EXTENSIONSExtensions [X] TEMPLATE Templates [X] TOOLS Tools I mean, if I enable Extensions, what happens? How do I figure out what happens? I have to read the Makefile, at which point having these options on a menu is pretty pointless. I mean, I can't even come up with a Google search to help me figure out what tools are involved here. There are some ports that do this very well. For example: [ ] NLS Use internationalized messages [ ] PAM Build with PAM support (server only) [ ] LDAP Build with LDAP authentication support [ ] MIT_KRB5 Build with MIT's kerberos support [ ] HEIMDAL_KRB5 Builds with Heimdal kerberos support [ ] OPTIMIZED_CFLAGS Builds with compiler optimizations (-O3) [X] XML Build with XML data type (server) [X] TZDATAUse internal timezone database (server) [ ] DEBUG Builds with debugging symbols [ ] ICU Use ICU for unicode collation (server) [ ] INTDATE Builds with 64-bit date/time type (server) I mean, a Google on ICU is liable to bring up all sorts of medical drama websites, but I can do a search for ICU unicode and find my answer on the first result. Not only am I told that optimized compiler flags are an option, but I'm told the exact one that will be used (-O3) The porters handbook doesn't seem to offer any helpful advice on these: http://www.freebsd.org/doc/en/books/porters-handbook/makefile-options.ht ml In fact, the examples it provides are excellent examples of doing it WRONG. Let me see about making a patch to the porters handbook to provide some advice ... +1,000,000 on your idea. Yes .. you are absolutely right ... even if you know your way around make gcc compiling software .. and even if you _really_ know your way around make gcc compiling software, there's no chance on earth that anyone can tell what does every single option on every single Makefile actually mean. As you pointed out: [ ] BRG [X] QFZ means _nothing_ to 99.9% of the users... Be Really Grumpy? Buy Red Goggles? Quite Faster Zapping?? Quit Filtering Zealots?? This kind of things really hurts the good documentation reputation that FreeBSD has rightfully earned. And I do agree with you: I don't think there's any need for any new features in the ports infrastructure. I think it's just a matter of Makefile authors taking the time to describe their options. And once again .. this is the way to go for me too: There are some ports that do this very well. For example: [ ] NLS Use internationalized messages [ ] PAM Build with PAM support (server only) [ ] LDAP Build with LDAP authentication support [ ] MIT_KRB5 Build with MIT's kerberos support [ ] HEIMDAL_KRB5 Builds with Heimdal kerberos support [ ] OPTIMIZED_CFLAGS Builds with compiler optimizations (-O3) [X] XML Build with XML data type (server) [X] TZDATAUse internal timezone database (server) [
Re: committer please update cfengine ports?
Jo Rhett jrh...@netconsonance.com writes: I'm the maintainer for the cfengine port, and I've got two updates which need to be committed. http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/131040 Seems that the final patch cannot be retrieved from the PR. WBR -- Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ 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: missing tinderbox/scripts/sql/values.lp
mahonm...@googlemail.com wrote: On 2009-01-31 00:51:55, mahonm...@googlemail.com wrote: Creating package /var/ports/packages/All/tinderbox-3.1.2_2.tbz Registering depends: p5-DBD-Pg-2.10.7 postgresql-client-8.2.11 gettext-0.17_1 libiconv-1.11_1 p5-DBI-1.60.4 p5-Storable-2.18 p5-version-0.76 perl-5.8.9. Creating bzip'd tar ball in '/var/ports/packages/All/tinderbox-3.1.2_2.tbz' tar: tinderbox/scripts/sql/values.lp: Cannot stat: No such file or directory tar: Error exit delayed from previous errors. pkg_create: make_dist: tar command failed with code 256 *** Error code 1 Seriously, noone? The pkg-plist specifies this mysterious values.lp file but having downloaded and extraced the tarball manually from marcuscom.com, this file is nowhere to be seen. The file values.lp contains some patterns for the new log file markup support. This feature is already in the MarcusCom CVS but hasn't been released yet. Take a look at files/exta-webui-patch-3.1.2_to_20081227.diff. This patch adds some new webui feature from the CVS into the 3.1.2 release from marcuscom.com. HTH, Beat ___ 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: [kde-freebsd] Call for Testing KDE 4.2 for FreeBSD
On Monday 02 February 2009 12:01:10 David Naylor wrote:
On Sunday 01 February 2009 23:02:28 Martin Wilke wrote:
Howdy Guys,
The KDE FreeBSD team is happy to announce the first public
Call for Testing for KDE 4.2. Over the past weeks we have
focused on the complex and very time consuming task to get
KDE 4.2 running.
Please read UPDATING-area51 before you start your update.
To get KDE 4.2:
try
svn co https://kf.athame.co.uk/kde-freebsd/trunk/area51/
/path/to/area51
More info here:
https://kf.athame.co.uk/access.php
- Martin (on behalf of the KDE FreeBSD team)
Hi,
I'll get started on testing today. I however have this strange desire to
use USB2 (the new USB stack introduced to FreeBSD-Current).
Just finished compiling on FreeBSD 7.1 and have found the following problems:
1. The fonts are not being anti-aliased? (Using default fonts and Use
anti-aliasing: Enabled {with sub-pixel rendering [RGB]}).
2. Network Settings doesn't detect anything to do with FreeBSD (it probably
still needs to be told about FreeBSD).
3. ksudo does not install?
4. Samba config module doesn't find smb.conf by default. It should look in
multiple places?
5. When I was changing desktop effects X froze. It was a once off thing...
Items 1,2, 4, (5) probably qualify for a PR, can anyone confirm these?
Item 3 probably has something to do with our ports. I really prefer to use
(k)sudo (since ksu doesn't like root without a password). Item 4 should be
fixed with a patch (until upstream comes with a proper solution).
If you wait a few hours I'll see what I can do about providing patches for
items 3, 4.
Is KDE4 happy with USB2 (or to be more precise, is hald happy with USB2
yet)?
I'll try compile hald with USB2. If that doesn't work (i.e. starts taking
100% CPU on a core) then I will not persue the issue. I'm not sure ports has
been converted to handle the base system's libusb20 in -current?
Oh and I am still having problems with HTTPS and proxy. I am going to try put
up a Squid proxy and see if Squid behaves better then WinGate. And I am
hoping Qt 4.5 will fix this proxy/socks problem (if it will hurry up and get
released :-)).
Everything else is looking good :-) and working on the FreeBSD side.
Thanks
David
P.S. Any hope in getting Amarok 2 into ports with KDE 4.2. Last I saw it was
pending on a PR to fix mysql_embedded?
signature.asc
Description: This is a digitally signed message part.
