Re: Installing Openoffice.org-2-RC and bison conflicts
Clint Olsen wrote: > I'm trying to install openoffice, and some sub-portion of the port is > installing bison2, and later it tries to install bison and then it > complains about conflicting ports. How is one supposed to deal with > sub-port conflicts like these? Why do we /ever/ allow ports to have > conflicts with other ports? That seems broken from the start. I agree :-) See my proposal (2 Jun 2007 entry) at http://www.freebsd.org/cgi/query-pr.cgi?pr=100358&cat=ports regards, Hans Lambermont ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
temporally out of action
Hello. I've changed a work place. I have no computers for developing here yet and my developer copmputer (in az@ office) is unaccessable too. So I can do commits only from my home computer and only in free time at weekends (really rarely). I can read emails but don't expect any commits or actions from me while I decide the problems above. -- Dixi. Sem. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: temporally out of action
ok, good luck on getting caught up. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: FreeBSD Port: gpsd-2.32
Hi there! :-) Please advise some GPS module for use with the subject under FreeBSD! TIA, Stas ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange problem with skype on RELENG_6 KERNEL since the end of may.
On Thu, 14 Jun 2007 09:29:09 -0500
"[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> A RELENG_6 kernel from May 21 works fine with skype but boot a newer
> kernel and skype seems to be blocking port 80. Apache logs show
> nothing. I can find no logs errors anywhere but a telnet to port 80
> answers with what would seem to be binary chars. I close skype and
> all is back to normal. I had originally thought that it had to do
> with the new xorg installation but it seems to be something in the
> kernel. The configurations were the same, basically GENERIC with all
> the pf stuff.
Hi,
Skype has an option to listen on tcp/80 and tcp/443 for incoming connections,
because it assumes somehow that firewalls will be configured to allow that
traffic in (some Windowze world assumption, i guess).
In the tools menu, go to Options, Advanced, untick the option that reads "Use
port (sic) 80 and 443 as alternatives for incoming connections".
Apply, exit skype, restart it.
confirm with
sockstat -4 | grep skype | grep \*:80
that skype is NOT listening on port 80 (you shouldn't see any output back from
that cmd) ( similar for 443)
_
{Beto|Norberto|Numard} Meijome
RTFM and STFW before anything bad happens.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: gpsd-2.32
Hi, On Tue, Jun 19, 2007 at 05:17:35PM +0400, Stanislav Silnitski wrote: > Please advise some GPS module for use with the subject under FreeBSD! I use a BU353 with gpsd under FreeBSD, see http://www.usglobalsat.com/item.asp?itemid=60 It is based on the Profilic PL-2303 chipset, which is supported by the uplcom(4) driver. Regards, Brix -- Henrik Brix Andersen <[EMAIL PROTECTED]> pgpCFCHVzQR7n.pgp Description: PGP signature
Re: Installing Openoffice.org-2-RC and bison conflicts
On Mon, 18 Jun 2007 16:33:43 -0700
Clint Olsen <[EMAIL PROTECTED]> wrote:
> Ok, so I'm required to resolve this myself if I want to install this port?
force uninstall bison and install bison2. fix all dependencies to bison with
pkgdb -F. carry on with OO.
granted, it's broken, but hardly critical.
_
{Beto|Norberto|Numard} Meijome
UFOs are for real: the Air Force doesn't exist.
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/usr/ports/graphics/php5-ffmpeg
I think php5-ffmpeg is miscatergorized, as it deals with both video and audio, so should it not go the same place as ffmpeg is (multimedia)? -Mit ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange problem with skype on RELENG_6 KERNEL since the end of may.
On Tue, 2007-06-19 at 23:40 +1000, Norberto Meijome wrote: > > On Thu, 14 Jun 2007 09:29:09 -0500 > "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > A RELENG_6 kernel from May 21 works fine with skype but boot a newer > > kernel and skype seems to be blocking port 80. Apache logs show > > nothing. I can find no logs errors anywhere but a telnet to port 80 > > answers with what would seem to be binary chars. I close skype and > > all is back to normal. I had originally thought that it had to do > > with the new xorg installation but it seems to be something in the > > kernel. The configurations were the same, basically GENERIC with all > > the pf stuff. > > Hi, > > Skype has an option to listen on tcp/80 and tcp/443 for incoming connections, > because it assumes somehow that firewalls will be configured to allow that > traffic in (some Windowze world assumption, i guess). > > In the tools menu, go to Options, Advanced, untick the option that reads "Use > port (sic) 80 and 443 as alternatives for incoming connections". > > Apply, exit skype, restart it. > > confirm with > > sockstat -4 | grep skype | grep \*:80 > > that skype is NOT listening on port 80 (you shouldn't see any output back from > that cmd) ( similar for 443) > Doesn't this imply that the OP was running Skype as root? signature.asc Description: This is a digitally signed message part
Re: Installing Openoffice.org-2-RC and bison conflicts
On Jun 19, Norberto Meijome wrote: > force uninstall bison and install bison2. fix all dependencies to bison > with pkgdb -F. carry on with OO. > > granted, it's broken, but hardly critical. Actually, as I mentioned to Chuck yesterday, I did a bit of creative Googling, and it was because my system (old 5.5-STABLE) had a default bison dependency set to devel/bison. Changing that in /usr/ports/Mk/bsd.port.mk to bison2 fixed the issue. I appreciate all the help! Thanks, -Clint ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange problem with skype on RELENG_6 KERNEL since the end of may.
Tom Evans wrote: On Tue, 2007-06-19 at 23:40 +1000, Norberto Meijome wrote: On Thu, 14 Jun 2007 09:29:09 -0500 "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: A RELENG_6 kernel from May 21 works fine with skype but boot a newer kernel and skype seems to be blocking port 80. Apache logs show nothing. I can find no logs errors anywhere but a telnet to port 80 answers with what would seem to be binary chars. I close skype and all is back to normal. I had originally thought that it had to do with the new xorg installation but it seems to be something in the kernel. The configurations were the same, basically GENERIC with all the pf stuff. Hi, Skype has an option to listen on tcp/80 and tcp/443 for incoming connections, because it assumes somehow that firewalls will be configured to allow that traffic in (some Windowze world assumption, i guess). In the tools menu, go to Options, Advanced, untick the option that reads "Use port (sic) 80 and 443 as alternatives for incoming connections". Apply, exit skype, restart it. confirm with sockstat -4 | grep skype | grep \*:80 that skype is NOT listening on port 80 (you shouldn't see any output back from that cmd) ( similar for 443) Doesn't this imply that the OP was running Skype as root? Yes if the sysctl's below net.inet.ip.portrange all have there default values. Tom ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
xrandr returns failed request with radeon driver
I have submitted a problem report about my problems with xrandr/radeon. > http://www.freebsd.org/cgi/query-pr.cgi?pr=113861 $ xrandr X Error of failed request: BadRequest (invalid request code or no such operation) Major opcode of failed request: 154 (RANDR) Minor opcode of failed request: 6 () Serial number of failed request: 9 Current serial number in output stream: 9 Does anyone else have this problem? ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD Port: mysql-server-3.23.59.n.20050301_3
Bob wrote: > Using the apache port as the standard example of how ports should be > installed > I have noticed 2 things wrong with the mysql-server port. > > First the port allocates the location for the databases to /var/db/mysql. > This location has no space allocated to hold database data. > It should be changed to /usr/local/mysql > > Next the mysql manual should be included in the port just like the apache > manual is. > > These are not technical changes but will make the FBSD port of mysql more > easy to use. > > Looking for feedback from the port team about these suggestions. Ah, you are back on the mailinglists! For the record (beyond the responses from people that already did reply): You are referring to an old release of MySQL in your subject; this is no longer supported (afair) by the MySQL team and you are encouraged to chase the latest GA release (which is 5.0.41 at the moment). Regards, Remko -- Kind regards, Remko Lodder ** [EMAIL PROTECTED] FreeBSD** [EMAIL PROTECTED] /* Quis custodiet ipsos custodes */ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
/usr/ports/databases/py-pyPgSQL Makefile changes
Attached is a patch to honour PKGNAMEPREFIX for py-pyPgSQL
--
Email: [EMAIL PROTECTED] Contact me for ICQ,MSN,AIM,Yahoo,Jabber
-- --
When things can't get any worse, they simplify themselves by getting a
whole lot worse then complicated. A complete and utter disaster is the
simplest thing in the world; it's preventing one that's complex.
(Janet Morris)
--- Makefile 2007/06/19 23:48:44 1.1
+++ Makefile 2007/06/19 23:49:18
@@ -10,7 +10,7 @@
CATEGORIES= databases python
MASTER_SITES= ${MASTER_SITE_SOURCEFORGE}
MASTER_SITE_SUBDIR= pypgsql
-PKGNAMEPREFIX= py-
+PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
MAINTAINER= [EMAIL PROTECTED]
COMMENT= A Python DB-API 2 compliant library for using PostgreSQL databases
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Generating patch files
Hi, I just started creating my first port for a program names qtpfsgui. Currently, there are several files to patch. Usually I would run "diff -r" to create one large patch, but the build system -- and the rules ,) -- expect a separate diff for each file to be patched. Is there an easy way to create this set of files, i.e. cutting the patch into pieces and naming the files accordingly? I looked through the handbook and various tools, but couldn't find the right one. Or did I miss the point here? Regards, -- Steffen Beyer <[EMAIL PROTECTED]> GnuPG key fingerprint: CA00 1611 242B 89D4 E643 E235 05F3 7689 DD3E EB26 Public key available upon request or at http://wwwkeys.de.pgp.net ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Strange problem with skype on RELENG_6 KERNEL since the end of may.
On Tue, 19 Jun 2007 17:26:59 +0100
Tom Evans <[EMAIL PROTECTED]> wrote:
> Doesn't this imply that the OP was running Skype as root?
touche.
but from what OP described, that's what was happening... :D ouch :D
_
{Beto|Norberto|Numard} Meijome
"Any society that would give up a little liberty to gain a little security will
deserve neither and lose both."
Benjamin Franklin
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Generating patch files
Steffen Beyer wrote: Hi, I just started creating my first port for a program names qtpfsgui. Currently, there are several files to patch. Usually I would run "diff -r" to create one large patch, but the build system -- and the rules ,) -- expect a separate diff for each file to be patched. Is there an easy way to create this set of files, i.e. cutting the patch into pieces and naming the files accordingly? I looked through the handbook and various tools, but couldn't find the right one. Or did I miss the point here? Regards, textproc/makepatch port will automate the generation of diff files. # makepatch -diff="diff -ruN" -nomanifest old-dir new-dir will do the majority of your work. jmc ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Generating patch files
On Wed, Jun 20, 2007 at 02:25:20AM +0200, Steffen Beyer wrote:
> Is there an easy way to create this set of files, i.e. cutting the patch
> into pieces and naming the files accordingly? I looked through the
> handbook and various tools, but couldn't find the right one.
Make sure that the directory files exist, Go to the ${WRKSRC}, and
run "makediff path/and/file.extension"
Edwin
--
Edwin Groothuis |Personal website: http://www.mavetju.org
[EMAIL PROTECTED]| Weblog: http://www.mavetju.org/weblog/
#!/bin/sh
filename=$1
filesdir=../../files
if [ -z "`echo ${filename} | grep _`" ]; then
patchfile="${filesdir}/patch-`echo ${filename} | sed -e 's/\//__/g'`"
else
patchfile="${filesdir}/patch-`echo ${filename} | sed -e 's/\//_/g'`"
fi
test -f ${filename}.orig || cp ${filename} ${filename}.orig
vi ${filename}
p=`grep -l " ${filename}" ${filesdir}/*`
test ! -z "${p}" && patchfile=${p}
diff -u ${filename}.orig ${filename} > ${patchfile}
echo "Saving diff to ${patchfile}"
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: xrandr returns failed request with radeon driver
On Tue, 19 Jun 2007 20:52:51 +0200
"[LoN]Kamikaze" <[EMAIL PROTECTED]> wrote:
> I have submitted a problem report about my problems with xrandr/radeon.
>
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=113861
>
> $ xrandr
> X Error of failed request: BadRequest (invalid request code or no such
> operation)
> Major opcode of failed request: 154 (RANDR)
> Minor opcode of failed request: 6 ()
> Serial number of failed request: 9
> Current serial number in output stream: 9
>
> Does anyone else have this problem?
ah...I thought I was using randr in the wrong way , was meaning to dig into it
later.
$ xrandr
X Error of failed request: BadRequest (invalid request code or no such
operation)
Major opcode of failed request: 156 (RANDR)
Minor opcode of failed request: 6 ()
Serial number of failed request: 9
Current serial number in output stream: 9
$ uname -a
FreeBSD ayiin.octantis.com.au 6.2-STABLE FreeBSD 6.2-STABLE #8: Fri Jun 15
22:08:03 EST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/AYIIN i386
[EMAIL PROTECTED]:0:0: class=0x03 card=0x058e1014 chip=0x31501002 rev=0x00
hdr=0x00
vendor = 'ATI Technologies Inc'
device = 'M24 1P Radeon Mobility X600'
class = display
subclass = VGA
running xorg 7.2, AGP built in but no DRM (it is a bit unstable for my liking
right now.)
Let me know if you need any more info.
Regards,
B
_
{Beto|Norberto|Numard} Meijome
"The people have always some champion whom they set over them and nurse into
greatness...
This and no other is the root from which a tyrant springs; when he first
appears he is a protector."
Plato
I speak for myself, not my employer. Contents may be hot. Slippery when wet.
Reading disclaimers makes you go blind. Writing them is worse. You have been
Warned.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Generating patch files
Steffen Beyer wrote:
Currently, there are several files to patch. Usually I would run "diff
-r" to create one large patch, but the build system -- and the rules ,)
-- expect a separate diff for each file to be patched.
Is there an easy way to create this set of files, i.e. cutting the patch
into pieces and naming the files accordingly? I looked through the
handbook and various tools, but couldn't find the right one.
Maybe you could use 'make makepatch':
lama> grep makepatch /usr/ports/Mk/bsd.port.mk -B4 -A12 | sed 's/ / /g'
# Look for ${WRKSRC}/.../*.orig files, and (re-)create
# ${FILEDIR}/patch-* files from them.
.if !target(makepatch)
makepatch:
@cd ${.CURDIR} && ${MKDIR} ${FILESDIR}
@(cd ${WRKSRC}; \
for i in `find . -type f -name '*.orig'`; do \
ORG=$$i; \
NEW=$${i%.orig}; \
OUT=${FILESDIR}`${ECHO} $${NEW} | \
${SED} -e 's|/|__|g' \
-e 's|^\.__|/patch-|'`; \
${ECHO} ${DIFF} -ud $${ORG} $${NEW} '>' $${OUT}; \
${DIFF} -ud $${ORG} $${NEW} > $${OUT} || ${TRUE}; \
done \
)
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: will someone please commit cfengine-2.2.1 ?
On Jun 9, 2007, at 5:15 AM, Sergei Kolobov wrote: I will commit this myself very shortly. Thanks! I would like to include rcNG script for Cfengine in addition to your patch with this upgrade, and testing that right now. It should not take long. cfengine doesn't use an rc script as such. It's designed to be run from cron... -- Jo Rhett senior geek Silicon Valley Colocation Support Phone: 408-400-0550 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
