Re: Port comparison failed
Eric ha scritto: it happens when i run portsnap and then get new ports via: pkg_version -v | grep \ Use: pkg_version -Ivl'' -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Support for KDE in compiz?
Hi, Is there any plan for KDE support in compiz-fusion? Best regards, Willy Picard -- Willy Picarde-mail: [EMAIL PROTECTED] Dept. of Information Technology www:http://www.kti.ae.poznan.pl/ The Poznan University of Economics tel:+48 61 848 05 49 Mansfelda 4, 60-854 Poznan, Poland fax:+48 61 848 38 40 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port comparison failed
Kirill Ponomarew ha scritto: Please note, it works only if you have updated INDEX file, if not, just use pkg_version -vL= He said he used that command just after portsnap, so it is. -- Alex Dupre ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port comparison failed
On Thu, Sep 20, 2007 at 09:49:05AM +0200, Alex Dupre wrote: Eric ha scritto: it happens when i run portsnap and then get new ports via: pkg_version -v | grep \ Use: pkg_version -Ivl'' Please note, it works only if you have updated INDEX file, if not, just use pkg_version -vL= -Kirill ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
mail/websieve -- doesn't get along with apache22
-BEGIN PGP SIGNED MESSAGE- Hash: RIPEMD160 Dear all, The mail/websieve port has a bug when installing with apache22 -- it registers a RUN_DEPENDS on /usr/local/www/cgi-bin and tries to install whatever the selected version of apache is to fulfil it. Of course, apache22 uses /usr/local/www/apache22/cgi-bin so that's never going to work. According to my reading of the porter's handbook, I think this port shouldn't have any explicit dependency on any web server --- websieve just installs a bunch of perl CGI scripts. I'll submit a patch to make that so shortly. However my question is: can I use a generic cgi-bin dir as the location for the files to go into, or should I be putting everything into /usr/local/www/websieve ? If I can use a generic cgi-bin directory, should that be /usr/local/www/cgi-bin ? Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. Flat 3 7 Priory Courtyard PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW, UK -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.4 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG8jd23jDkPpsZ+VYRA7a7AJ9Tp2RLF1WBxfSfjcbe5Vald1QuhACfd+gT GiDFaTXamFVNCLfZuFYq7CM= =4AyR -END PGP SIGNATURE- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
xorg 7.3 upgrade: kde lost keyboard
Hi, I am having some trouble after the xorg update to 7.3. I did the suggested # portupgrade -R x11/xorg but xorg kept complaining about ABI (keyboard and nv drivers) issues which were only resolved with # portupgrade -Rf x11/xorg Then, when I finally got KDE to startup, the keyboard is no longer responding. I even did # portupgrade -Rf x11/xorg x11/kde3 but to no vail. Keyboard responds when KDE starts (I can click OK on the lack-of-COMPOSITE-extension complain dialogs) but it stops responding right away. Has anyone had this problem? My next step will be # portupgrade -Rrf x11/xorg if I can't find a solution to this problem. Regards, -- Mario S F Ferreira - DF - Brazil - I guess this is a signature. feature, n: a documented bug | bug, n: an undocumented feature ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Support for KDE in compiz?
On Thu, 2007-09-20 at 09:58 +0200, Willy Picard wrote: Hi, Is there any plan for KDE support in compiz-fusion? All that KDE support currently gets you as far as I can tell, is kde-window-decorator, at least from compiz directly. I have a compiz port on my tinderbox now with KDE support enabled. The big problem that I have is figuring out a way to optionally enable KDE support. The only solution I have at the moment is a manual knob. I don't see any way to do this with the options framework... The other part would be compizconfig-backends-kconfig which I haven't worked on yet, but shouldn't take long assuming I have a reasonable solution for compiz. robert. Best regards, Willy Picard signature.asc Description: This is a digitally signed message part
xorg 7.3 upgrade: kde lost keyboard
Hi, I am having some trouble after the xorg update to 7.3. I did the suggested # portupgrade -R x11/xorg but xorg kept complaining about ABI (keyboard and nv drivers) issues which were only resolved with # portupgrade -Rf x11/xorg Then, when I finally got KDE to startup, the keyboard is no longer responding. I even did # portupgrade -Rf x11/xorg x11/kde3 but to no vail. Keyboard responds when KDE starts (I can click OK on the lack-of-COMPOSITE-extension complain dialogs) but it stops responding right away. Has anyone had this problem? My next step will be # portupgrade -Rrf x11/xorg if I can't find a solution to this problem. Regards, -- Mario S F Ferreira - DF - Brazil - I guess this is a signature. feature, n: a documented bug | bug, n: an undocumented feature ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Support for KDE in compiz?
On Thu, 20 Sep 2007, Robert Noland wrote: The big problem that I have is figuring out a way to optionally enable KDE support. The only solution I have at the moment is a manual knob. I don't see any way to do this with the options framework... What about this would make it hard to do with options? Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Support for KDE in compiz?
On Thu, 2007-09-20 at 14:49 -0700, Doug Barton wrote: On Thu, 20 Sep 2007, Robert Noland wrote: The big problem that I have is figuring out a way to optionally enable KDE support. The only solution I have at the moment is a manual knob. I don't see any way to do this with the options framework... What about this would make it hard to do with options? For KDE support I need USE_KDEBASE_VER, which must be defined before bsd.port.pre.mk. I haven't come up with a way to make it work with a test after options have been tested. robert. Doug signature.asc Description: This is a digitally signed message part
www/apache22 seems to have a patch problem.
I've cvsuped the ports tree a couple of times and can't update apache22. I hope that I'm not the only one. === Applying FreeBSD patches for apache-2.2.6_1 3 out of 4 hunks failed--saving rejects to Makefile.in.rej = Patch patch-Makefile.in failed to apply cleanly. *** Error code 1 thanks, ed ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port comparison failed
On Wed, 19 Sep 2007, Eric wrote: Anyone have a way to fix this: snip portsnap output Building new INDEX files... done. portconf-1.2! Comparison failed portmaster-1.9 ! Comparison failed Version 1.9 is really old, we're up to version 1.20 now. Are you sure your port tree is up to date? it happens when i run portsnap and then get new ports via: pkg_version -v | grep \ I can't think of any reason that wouldn't work, which leads me to believe that you've got bigger issues lurking somewhere. i tried uninstalling and then reinstalling the ports above but it didnt fix the issue. I assume that after you reinstalled portmaster that you had version 1.20? I use portmaster to update ports. I do not have any other port management tool installed. Before I wrote the -L feature for portmaster, I used to use 'pkg_version -v -L=' as an alias to find out what needed rebuilding. Assuming you're using version 1.20 of portmaster, you might want to check the man page and try the -L option to see if portmaster can find the problem. hth, Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/apache22 seems to have a patch problem.
On Thu, Sep 20, 2007 at 06:12:47AM -0500, [EMAIL PROTECTED] wrote: I've cvsuped the ports tree a couple of times and can't update apache22. I hope that I'm not the only one. === Applying FreeBSD patches for apache-2.2.6_1 3 out of 4 hunks failed--saving rejects to Makefile.in.rej = Patch patch-Makefile.in failed to apply cleanly. *** Error code 1 Are you using -CURRENT? If so, see the following for the issue: http://lists.freebsd.org/pipermail/freebsd-current/2007-September/077163.html Otherwise, I cannot reproduce the patch problem you describe, either on -CURRENT or RELENG_6. -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port comparison failed
Doug Barton wrote: On Wed, 19 Sep 2007, Eric wrote: Anyone have a way to fix this: snip portsnap output Building new INDEX files... done. portconf-1.2! Comparison failed portmaster-1.9 ! Comparison failed Version 1.9 is really old, we're up to version 1.20 now. Are you sure your port tree is up to date? it happens when i run portsnap and then get new ports via: pkg_version -v | grep \ I can't think of any reason that wouldn't work, which leads me to believe that you've got bigger issues lurking somewhere. i tried uninstalling and then reinstalling the ports above but it didnt fix the issue. I assume that after you reinstalled portmaster that you had version 1.20? I use portmaster to update ports. I do not have any other port management tool installed. Before I wrote the -L feature for portmaster, I used to use 'pkg_version -v -L=' as an alias to find out what needed rebuilding. Assuming you're using version 1.20 of portmaster, you might want to check the man page and try the -L option to see if portmaster can find the problem. hth, Doug somehow i had /var/db/pkg entries for 1.9 and 1.20. I deleted the 1.9. thanks for the info. things seem to look good now Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portsnap serving up bad snapshots?
On Wed, Sep 19, 2007 at 12:34:22PM -0700, Marcus Reid wrote: Hi, I've tried this on a couple of different machines a few times over the last couple of days, and keep getting the same results. Starting with an empty /var/db/portsnap : [EMAIL PROTECTED] /var/db]# portsnap fetch Looking up portsnap.FreeBSD.org mirrors... 4 mirrors found. Fetching public key from portsnap3.freebsd.org... done. Fetching snapshot tag from portsnap3.freebsd.org... done. Fetching snapshot metadata... done. Fetching snapshot generated at Tue Sep 18 17:22:37 PDT 2007: 1d76db54d472a78981f30c134f34eea49141d183d48127100% of 49 MB 90 kBps 00m00s Extracting snapshot... done. Verifying snapshot integrity... gunzip: snap/2bafbd0d8edc7a7cfa7e19833986ae4032f82006fd0d65cba9c4a75b432b5c8e.gz: unexpected end of file gunzip: snap/2bafbd0d8edc7a7cfa7e19833986ae4032f82006fd0d65cba9c4a75b432b5c8e.gz: uncompress failed snapshot corrupt. Hi Again, Just thought I'd set the record straight.. This turned out to be a regression in libarchive that broke bsdtar in -CURRENT. It has since been backed out. There was no problem with portsnap. Marcus ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/apache22 seems to have a patch problem.
On Thu, 20 Sep 2007, [EMAIL PROTECTED] wrote: I've cvsuped the ports tree a couple of times and can't update apache22. I hope that I'm not the only one. === Applying FreeBSD patches for apache-2.2.6_1 3 out of 4 hunks failed--saving rejects to Makefile.in.rej = Patch patch-Makefile.in failed to apply cleanly. *** Error code 1 When a port is not generally known to be broken (and this one isn't), all the mysterious patch problems I have ever found came from trying to use cp at some point to update the ports tree. I suggest you remove the entire apache22 directory and cvsup again to be certain that you do not have old patch debris in the port. -- Lars Eighner http://www.larseighner.com/index.html 8800 N IH35 APT 1191 AUSTIN TX 78753-5266 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: www/apache22 seems to have a patch problem.
Lars Eighner writes: === Applying FreeBSD patches for apache-2.2.6_1 3 out of 4 hunks failed--saving rejects to Makefile.in.rej = Patch patch-Makefile.in failed to apply cleanly. *** Error code 1 When a port is not generally known to be broken (and this one isn't), all the mysterious patch problems I have ever found came from trying to use cp at some point to update the ports tree. I suggest you remove the entire apache22 directory and cvsup again to be certain that you do not have old patch debris in the port. Agreed. Robert Huff ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
