Make index fails
Hi, I just updated my ports tree with csup but make index fails: Generating INDEX-7 - please wait.."Makefile", line 114: Inconsistent operator for post-patch make: fatal errors encountered -- cannot continue ===> archivers/rpm5 failed *** Error code 1 1 error Cheers, Remko C. ___ 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: Gnucash-2.2.7_2 - 7.2 - Core dump
On Mon, Apr 13, 2009 at 12:45:30PM +0200, Guido Falsi wrote: >> >> Any clue ? > > I'm having the same problem both with 7.2 and 8. It crashes when opening > any account page, I think the problem is the glib update to 2.20, or > perhaps the gtk. Gnucash already had this kind of problem in the past. > After finding this: https://bugzilla.redhat.com/show_bug.cgi?id=474511 which looks exactly like our problem, I noticed a newer version of gnucash was also available, incorporating a fix. I filed this PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=133721 I hope the port maintainer will look at it in a few days at most, I think this is an update we would like to have before 7.2, since the port is broken otherwise. Is this possible? Is there anything I can do to speed things up? -- Guido Falsi ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 14 Apr 2009, Michal Varga wrote: MV> On Tue, Apr 14, 2009 at 3:13 AM, Dmitry Morozovsky wrote: MV> > Dear Joe Marcus, MV> > MV> > DM> JMC> What versions of gnome-keyring and seahorse do you have? MV> > DM> MV> > DM> ma...@revamp:/usr/ports> pkg_info | egrep 'gnome-keyring|seahorse' MV> > DM> gnome-keyring-2.26.0 A program that keeps passwords and other secrets MV> > DM> seahorse-2.26.0 GNOME application for managing encryption keys (PGP, SSH) MV> > MV> > After MV> > MV> > portupgrade -f seahorse gnome-keyring MV> > MV> > and reboot MV> > MV> > still the same effect... MV> > MV> > Of course, I can wipe packages installed and set it up from scratch, but I MV> > would prefer a bit safer way if at all possible ;-) MV> > MV> Well, I have no idea what a "Terminal remote login" in this particular MV> context is, so this may not be of any help, but I've seen this issue MV> before: MV> MV> "Before the upgrade, I had once pop-up asking for my key passphrase, then MV> let me use this private key during my (home) session without further asking.. MV> Now, when I try to connect to the host which even possibly want to check MV> whether I want to present some key there, I got the pop-up. I even checked that MV> I can connect to the host in question using plain xterm, and have usual MV> password qiery." MV> MV> I've been in similiar situation some time ago, when new MV> gnome-keyring/seahorse (it started with one of the recent versions, MV> don't remember exactly when, but definitely before 2.26 was MV> introduced) for some surely interesting reason insisted on creating a MV> very own keyring every other reboot - while originally you were using MV> one default keyring (let's call it "default") for storing your MV> passwords, now gnome-keyring kept creating a new one named "login" and MV> always set it as the default one. MV> MV> That "login" keyring was even more special in that that nothing stored MV> in it ever worked, it still kept asking for passwords and even then MV> was not able to use them (and lost them on the next reboot anyway.. MV> Maybe that's a feature, don't know, don't care). I've run into this on MV> a few different machines, every time I needed to open 'seahorse', get MV> to Passwords tab, delete the "login" keyring, set the original MV> "default" as the default keyring (first time I wiped them all and MV> created a clean one to be sure, but as it turned out later, this MV> wasn't needed), after that, passwords worked fine again. This MV> procedure again and again for a few days/reboots, until seahorse MV> miraculously stopped this madness and let my default keyring be, well, MV> default (yes, just like that). MV> MV> Anyway, if you weren't there yet, check seahorse gui for what keyring MV> are you really using, maybe you've hit the same issue with the "login" MV> stupidity.. Yes, seahorse shows me two keyrings; however, deleting "login" one does not fix the situation: if in the Terminal I try to open tab which ssh's to outer host, I immediately got the popup with "There was an error creating the child process for this terminal" nothing in this tab is started, and tab is just hanging. "login" keyring sometimes got recreated, sometimes not, but the effect above is totally reproducible. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.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"
PR for devel/jsmin not answered by maintainer
Hello, Almost a month ago I filed a PR for jsmin, which is not building because teh distfile(a .c file) was modified upstram for a new version, so fails checksum rendering the port effectively broken. It was automatically assighen to the port mantainer, but no action was taken, is someone looking at it? This is the PR: http://www.freebsd.org/cgi/query-pr.cgi?pr=132775 Is it correct for me to ask for maintainer timeout to be applied? Thanks in advance to anyone looking at this. -- Guido Falsi ___ 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 which are currently scheduled for deletion
Chris Rees ha scritto: portname: audio/rosegarden description:The Rosegarden Editor and Sequencer suite maintainer: po...@freebsd.org deprecated because: tcl82 support is going to be dropped expiration date:2009-04-22 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=rosegarden Woah! How do I save this? I'm thinking we could replace this with the new version (ironically called 1.7.3 rather than 2.1). I have a port for the latest version of rosegarden on my PC, waiting for being finished and committed. -- Alex Dupre ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, Apr 14, 2009 at 12:24 PM, Dmitry Morozovsky wrote: > On Tue, 14 Apr 2009, Michal Varga wrote: > Yes, seahorse shows me two keyrings; however, deleting "login" one does not > fix > the situation: if in the Terminal I try to open tab which ssh's to outer host, > I immediately got the popup with > > "There was an error creating the child process for this terminal" > > nothing in this tab is started, and tab is just hanging. > Out of curiosity, unrelated to your issue - if this is about interactive ssh [shell] session, do you mean Gnome Terminal? I wasn't aware it can do anything on its own with ssh, normally I run the regular ssh client inside. How do you ssh directly from Gnome Terminal (if that's the one you mean) with gnome-keyring/seahorse capabilities? m. ___ 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"
Possibly unbuildable ports reminder
Dear porters, This is just a reminder to please periodically check the list of unbuildable ports at http://pointyhat.freebsd.org/errorlogs/ . A list by MAINTAINER is http://people.freebsd.org/~fenner/errorlogs/ so you can easily check the status of ports that you maintain. In addition, the list of ports with no MAINTAINER with build problems is http://people.freebsd.org/~fenner/errorlogs/po...@freebsd.org.html Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. Thanks for your help! Bill "annoying port email" Fenner ___ 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: PR for devel/jsmin not answered by maintainer
On Tue, Apr 14, 2009 at 01:00:51PM +0200, Guido Falsi wrote: > Hello, > > Almost a month ago I filed a PR for jsmin, which is not building > because teh distfile(a .c file) was modified upstram for a new version, > so fails checksum rendering the port effectively broken. > > It was automatically assighen to the port mantainer, but no action was > taken, is someone looking at it? > > This is the PR: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=132775 > > Is it correct for me to ask for maintainer timeout to be applied? > > Thanks in advance to anyone looking at this. Yes, it is in maintainer timeout so I'll grab it and commit it after the freeze is over (it's not quite broken yet because the old .c file is still available on the FreeBSD mirror). Sorry for the delay. -- WXS ___ 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: PR for devel/jsmin not answered by maintainer
On Tue, Apr 14, 2009 at 09:23:27AM -0400, Wesley Shields wrote: > On Tue, Apr 14, 2009 at 01:00:51PM +0200, Guido Falsi wrote: > > http://www.freebsd.org/cgi/query-pr.cgi?pr=132775 > > > > Is it correct for me to ask for maintainer timeout to be applied? > > > > Thanks in advance to anyone looking at this. > > Yes, it is in maintainer timeout so I'll grab it and commit it after the > freeze is over (it's not quite broken yet because the old .c file is > still available on the FreeBSD mirror). > > Sorry for the delay. No problem, thank you for the quick reply. I'm in no hurry to get that committed, so after the freeze is ok. I just wnated to make sure someone was following it. Thank you again for your kind support. -- Guido Falsi ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 14:24 +0400, Dmitry Morozovsky wrote: > On Tue, 14 Apr 2009, Michal Varga wrote: > > MV> On Tue, Apr 14, 2009 at 3:13 AM, Dmitry Morozovsky wrote: > MV> > Dear Joe Marcus, > MV> > > MV> > DM> JMC> What versions of gnome-keyring and seahorse do you have? > MV> > DM> > MV> > DM> ma...@revamp:/usr/ports> pkg_info | egrep 'gnome-keyring|seahorse' > MV> > DM> gnome-keyring-2.26.0 A program that keeps passwords and other > secrets > MV> > DM> seahorse-2.26.0 GNOME application for managing encryption keys > (PGP, SSH) > MV> > > MV> > After > MV> > > MV> > portupgrade -f seahorse gnome-keyring > MV> > > MV> > and reboot > MV> > > MV> > still the same effect... > MV> > > MV> > Of course, I can wipe packages installed and set it up from scratch, > but I > MV> > would prefer a bit safer way if at all possible ;-) > MV> > > MV> Well, I have no idea what a "Terminal remote login" in this particular > MV> context is, so this may not be of any help, but I've seen this issue > MV> before: > MV> > MV> "Before the upgrade, I had once pop-up asking for my key passphrase, then > MV> let me use this private key during my (home) session without further > asking.. > MV> Now, when I try to connect to the host which even possibly want to check > MV> whether I want to present some key there, I got the pop-up. I even > checked that > MV> I can connect to the host in question using plain xterm, and have usual > MV> password qiery." > MV> > MV> I've been in similiar situation some time ago, when new > MV> gnome-keyring/seahorse (it started with one of the recent versions, > MV> don't remember exactly when, but definitely before 2.26 was > MV> introduced) for some surely interesting reason insisted on creating a > MV> very own keyring every other reboot - while originally you were using > MV> one default keyring (let's call it "default") for storing your > MV> passwords, now gnome-keyring kept creating a new one named "login" and > MV> always set it as the default one. > MV> > MV> That "login" keyring was even more special in that that nothing stored > MV> in it ever worked, it still kept asking for passwords and even then > MV> was not able to use them (and lost them on the next reboot anyway.. > MV> Maybe that's a feature, don't know, don't care). I've run into this on > MV> a few different machines, every time I needed to open 'seahorse', get > MV> to Passwords tab, delete the "login" keyring, set the original > MV> "default" as the default keyring (first time I wiped them all and > MV> created a clean one to be sure, but as it turned out later, this > MV> wasn't needed), after that, passwords worked fine again. This > MV> procedure again and again for a few days/reboots, until seahorse > MV> miraculously stopped this madness and let my default keyring be, well, > MV> default (yes, just like that). > MV> > MV> Anyway, if you weren't there yet, check seahorse gui for what keyring > MV> are you really using, maybe you've hit the same issue with the "login" > MV> stupidity.. > > Yes, seahorse shows me two keyrings; however, deleting "login" one does not > fix > the situation: if in the Terminal I try to open tab which ssh's to outer > host, > I immediately got the popup with > > "There was an error creating the child process for this terminal" > > nothing in this tab is started, and tab is just hanging. > > "login" keyring sometimes got recreated, sometimes not, but the effect above > is > totally reproducible. If I am following this correctly, the functionality you are talking about is actually provided by seahorse-agent, which is installed with the seahorse-plugins port now. Unless something has changed with the default session (and I don't think it has, since my keyrings still work) we wrap the session with ssh-agent and seahorse-agent if they are found. robert. -- Robert Noland FreeBSD signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 14 Apr 2009, Michal Varga wrote: MV> > Yes, seahorse shows me two keyrings; however, deleting "login" one does not fix MV> > the situation: if in the Terminal I try to open tab which ssh's to outer host, MV> > I immediately got the popup with MV> > MV> > "There was an error creating the child process for this terminal" MV> > MV> > nothing in this tab is started, and tab is just hanging. MV> > MV> Out of curiosity, unrelated to your issue - if this is about MV> interactive ssh [shell] session, do you mean Gnome Terminal? MV> MV> I wasn't aware it can do anything on its own with ssh, normally I run MV> the regular ssh client inside. How do you ssh directly from Gnome MV> Terminal (if that's the one you mean) with gnome-keyring/seahorse MV> capabilities? Yes, it's Gnome Terminal, see $SUBJ ;-) I just filled 'ssh -e none host' in execute command field. Before upgrade to 2.26 everything is worked like a charm -- on a first external connect, seahorse popup appears, asks me for a passphrase, and subsequent external sessions works automagically. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, Apr 14, 2009 at 5:34 PM, Dmitry Morozovsky wrote: > On Tue, 14 Apr 2009, Michal Varga wrote: > Yes, it's Gnome Terminal, see $SUBJ ;-) > > I just filled 'ssh -e none host' in execute command field. > > Before upgrade to 2.26 everything is worked like a charm -- on a first > external > connect, seahorse popup appears, asks me for a passphrase, and subsequent > external sessions works automagically. > I'm still puzzled with that, by execute command field i guess you mean "[x] run a custom command instead of my shell" in gnome-terminal preferences. Bud where'd you get the ssh/seahorse functionality? Let's assume the 'ssh' will run the first ssh in path, that is by default $ which ssh /usr/bin/ssh $ ssh -V OpenSSH_5.1p1 FreeBSD-20080901, OpenSSL 0.9.8e 23 Feb 2007 But where does your seahorse powered ssh client come from? m. ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 14 Apr 2009, Robert Noland wrote: [snip all] RN> > Yes, seahorse shows me two keyrings; however, deleting "login" one does not fix RN> > the situation: if in the Terminal I try to open tab which ssh's to outer host, RN> > I immediately got the popup with RN> > RN> > "There was an error creating the child process for this terminal" RN> > RN> > nothing in this tab is started, and tab is just hanging. RN> > RN> > "login" keyring sometimes got recreated, sometimes not, but the effect above is RN> > totally reproducible. RN> RN> If I am following this correctly, the functionality you are talking RN> about is actually provided by seahorse-agent, which is installed with RN> the seahorse-plugins port now. Unless something has changed with the RN> default session (and I don't think it has, since my keyrings still work) RN> we wrap the session with ssh-agent and seahorse-agent if they are found. Aha! Yes, and seahorse-plugins was not installed; moreover, one of its dependencies (pth) conflicted with pth-hard installed previously. I'll try to clean this up and report the results. Thank you! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.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: HEADS UP: GNOME 2.26 available for FreeBSD
2009/4/14 Michal Varga : > On Tue, Apr 14, 2009 at 5:34 PM, Dmitry Morozovsky wrote: >> On Tue, 14 Apr 2009, Michal Varga wrote: > >> Yes, it's Gnome Terminal, see $SUBJ ;-) >> >> I just filled 'ssh -e none host' in execute command field. >> >> Before upgrade to 2.26 everything is worked like a charm -- on a first >> external >> connect, seahorse popup appears, asks me for a passphrase, and subsequent >> external sessions works automagically. >> > I'm still puzzled with that, by execute command field i guess you mean > "[x] run a custom command instead of my shell" in gnome-terminal > preferences. Bud where'd you get the ssh/seahorse functionality? > > Let's assume the 'ssh' will run the first ssh in path, that is by default > > $ which ssh > /usr/bin/ssh > > $ ssh -V > OpenSSH_5.1p1 FreeBSD-20080901, OpenSSL 0.9.8e 23 Feb 2007 > > But where does your seahorse powered ssh client come from? It's an ssh agent, not an ssh client. I think it defines some SSH_* env variables at session opening, which are used by /usr/bin/ssh. -- Olivier Smedts _ ASCII ribbon campaign ( ) e-mail: oliv...@gid0.org- against HTML email & vCards X www: http://www.gid0.org- against proprietary attachments / \ "Il y a seulement 10 sortes de gens dans le monde : ceux qui comprennent le binaire, et ceux qui ne le comprennent pas." ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 21:05 +0400, Dmitry Morozovsky wrote: > On Tue, 14 Apr 2009, Robert Noland wrote: > > [snip all] > > RN> > Yes, seahorse shows me two keyrings; however, deleting "login" one does > not fix > RN> > the situation: if in the Terminal I try to open tab which ssh's to > outer host, > RN> > I immediately got the popup with > RN> > > RN> > "There was an error creating the child process for this terminal" > RN> > > RN> > nothing in this tab is started, and tab is just hanging. > RN> > > RN> > "login" keyring sometimes got recreated, sometimes not, but the effect > above is > RN> > totally reproducible. > RN> > RN> If I am following this correctly, the functionality you are talking > RN> about is actually provided by seahorse-agent, which is installed with > RN> the seahorse-plugins port now. Unless something has changed with the > RN> default session (and I don't think it has, since my keyrings still work) > RN> we wrap the session with ssh-agent and seahorse-agent if they are found. > > Aha! Yes, and seahorse-plugins was not installed; moreover, one of its > dependencies (pth) conflicted with pth-hard installed previously. I'll try to > clean this up and report the results. I had assumed you had x11/gnome2 installed which includes seahorse-plugins. I find people that expect to be using seahorse-agent are using the entire GNOME Desktop. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: FreeBSD ports which are currently scheduled for deletion
2009/4/14 Alex Dupre : > Chris Rees ha scritto: >>> >>> portname: audio/rosegarden >>> description: The Rosegarden Editor and Sequencer suite >>> maintainer: po...@freebsd.org >>> deprecated because: tcl82 support is going to be dropped >>> expiration date: 2009-04-22 >>> build errors: none. >>> overview: >>> http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=rosegarden >>> >> >> Woah! How do I save this? I'm thinking we could replace this with the >> new version (ironically called 1.7.3 rather than 2.1). > > I have a port for the latest version of rosegarden on my PC, waiting for > being finished and committed. > > -- > Alex Dupre > Hehe, glad I got this before I got too far with my efforts. Thanks for the warning. I would offer a hand, but I'm an amateur, and since you have an @freebsd email I'm guessing you're a regular. If you do want help, I'm here :D Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? ___ 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: mythtv 0.21 - trouble compiling the port
Hi, 2009/4/13 Bernhard Fröhlich : > Looks like another missing patch. Now i've double checked with your list > and this is the last missing one. (also taken from mythtv-frontend) > > http://home.bluelife.at/ports/mythtv/patch-libs-libmythtv-libmythtv.pro Yes, now 'make' in mythtv woks as expected. Thank you. :-) However, 'make install' fails if mysql is not running: Added group "mythtv". Added user "mythtv". Starting mysql. *** Unable to start mysqld *** Error code 1 Stop in /usr/ports/multimedia/mythtv. *** Error code 1 Stop in /usr/ports/multimedia/mythtv. *** Error code 1 Stop in /usr/ports/multimedia/mythtv. The port is lying about not being able to start mysql: r...@kg-quiet# /usr/local/etc/rc.d/mysql-server status mysql is running as pid 34965. If I run 'make install' with mysql running, it works as expected. I'm not really sure how this should be handled. Perphaps the port should just tell the user that it was unable to install the database, and tel her / hom how to do it manually? -- Regards, Torfinn Ingolfsen ___ 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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 14 Apr 2009, Joe Marcus Clarke wrote: JMC> > RN> If I am following this correctly, the functionality you are talking JMC> > RN> about is actually provided by seahorse-agent, which is installed with JMC> > RN> the seahorse-plugins port now. Unless something has changed with the JMC> > RN> default session (and I don't think it has, since my keyrings still work) JMC> > RN> we wrap the session with ssh-agent and seahorse-agent if they are found. JMC> > JMC> > Aha! Yes, and seahorse-plugins was not installed; moreover, one of its JMC> > dependencies (pth) conflicted with pth-hard installed previously. I'll try to JMC> > clean this up and report the results. JMC> JMC> I had assumed you had x11/gnome2 installed which includes JMC> seahorse-plugins. I find people that expect to be using seahorse-agent JMC> are using the entire GNOME Desktop. Well, I did ;-) Somehow during the upgrade gnome2 meta-port had been uninstalled, hence missing portupgrade -a. I'm now in progress of portupgrade -N gnome2, will report the results. Thank you! -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 14 Apr 2009, Joe Marcus Clarke wrote: JMC> I had assumed you had x11/gnome2 installed which includes JMC> seahorse-plugins. I find people that expect to be using seahorse-agent JMC> are using the entire GNOME Desktop. Another question: is there a way to avoid apache22 install (i have apache13 installed and have no current plans to upgrade) ? I tried to chase options but failed. -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 22:20 +0400, Dmitry Morozovsky wrote: > On Tue, 14 Apr 2009, Joe Marcus Clarke wrote: > > JMC> I had assumed you had x11/gnome2 installed which includes > JMC> seahorse-plugins. I find people that expect to be using seahorse-agent > JMC> are using the entire GNOME Desktop. > > Another question: is there a way to avoid apache22 install (i have apache13 > installed and have no current plans to upgrade) ? I tried to chase > options but failed. Not by using the meta-port. This is required for gnome-user-share which is now part of the GNOME Desktop. Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
Re: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 14 Apr 2009, Joe Marcus Clarke wrote: JMC> > JMC> I had assumed you had x11/gnome2 installed which includes JMC> > JMC> seahorse-plugins. I find people that expect to be using seahorse-agent JMC> > JMC> are using the entire GNOME Desktop. JMC> > JMC> > Another question: is there a way to avoid apache22 install (i have apache13 JMC> > installed and have no current plans to upgrade) ? I tried to chase JMC> > options but failed. JMC> JMC> Not by using the meta-port. This is required for gnome-user-share which JMC> is now part of the GNOME Desktop. Hmm, so currently there is no way to install gnome2 without requiring apache22? -- Sincerely, D.Marck [DM5020, MCK-RIPE, DM3-RIPN] [ FreeBSD committer: ma...@freebsd.org ] *** Dmitry Morozovsky --- D.Marck --- Wild Woozle --- ma...@rinet.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: HEADS UP: GNOME 2.26 available for FreeBSD
On Tue, 2009-04-14 at 23:22 +0400, Dmitry Morozovsky wrote: > On Tue, 14 Apr 2009, Joe Marcus Clarke wrote: > > JMC> > JMC> I had assumed you had x11/gnome2 installed which includes > JMC> > JMC> seahorse-plugins. I find people that expect to be using > seahorse-agent > JMC> > JMC> are using the entire GNOME Desktop. > JMC> > > JMC> > Another question: is there a way to avoid apache22 install (i have > apache13 > JMC> > installed and have no current plans to upgrade) ? I tried to chase > JMC> > options but failed. > JMC> > JMC> Not by using the meta-port. This is required for gnome-user-share which > JMC> is now part of the GNOME Desktop. > > Hmm, so currently there is no way to install gnome2 without requiring > apache22? Correct. You could, of course, go through the meta-port, and remove gnome-user-share on your own (i.e. build your own customized meta-port). Joe > -- Joe Marcus Clarke FreeBSD GNOME Team :: gn...@freebsd.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome signature.asc Description: This is a digitally signed message part
How to "portinstall -P" packages that alter ther names via PKGNAMESUFFIX?
Hello, we were looking for a way to manage efficiently the ports installed in our servers and we came up with the idea to set up a "builder" server on which we compile, install and test all ports. The rest of our servers set the PKG_SITES variable to "builder" and use "portinstall -P" and "portupgrade -P" for installations and upgrades. The setup works quite well and has saved us a lot of time and effort. Currently we are looking for ways to automate as much as possible the whole process. One of the problems we face is the initial installation of packages that alter their names, like sendmail+tls+sasl2+ldap+db46 and openldap-sasl-server. Seems like there is no obvious way to "portinstall -P" such packages. Falling back to "pkg_add -r full-URL" would be an ugly solution :-/ Any ideas? Cheers, Panagiotis -- Panagiotis J. ChristiasNetwork Management Center p.christ...@noc.ntua.grNational Technical Univ. of Athens, GREECE ___ 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-im/finch crashing on startup
Hi, First, some system details: [18:41][jos...@fgd135] % uname -a FreeBSD FGD135.localdomain 7.1-RELEASE-p4 FreeBSD 7.1-RELEASE-p4 #0: Sun Mar 22 12:35:36 UTC 2009 r...@i386-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC i386 I have just built the net-im/finch port (and libpurple) using the following configure options: BONJOUR=on "Enable mDNS support" DBUS=on "Enable DBUS bindings" GNUTLS=on "GNUTLS encryption support" NSS=off "Mozilla NSS encryption support" SASL=off "Cyrus SASL support (for jabberd)" PERL=off "Perl scripting" TCLTK=off "Tcl/Tk scripting" SAMETIME=off "The Lotus Sametime chat protocol" SILC=off "The Secure Internet Live Conferencing protocol" GG=off "The Gadu-Gadu chat protocol" IRC=off "The Internet Relay Chat protocol" JABBER=on "The Jabber/XMPP/Google Talk protocol" MSN=off "The MSN Messenger protocol" MYSPACE=off "The MySpaceIM protocol" NOVELL=off "The Novell GroupWise chat protocol" OSCAR=on "The AIM/ICQ/Oscar protocol" QQ=off "The Tercent QQ chat protocol" SIMPLE=off "The SIMPLE chat protocol" YAHOO=off "The Yahoo! Messenger protocol" ZEPHYR=off "The Zephyr chat protocol" As soon as I try and start finch, it loads for a brief second, but then I get a segmentation fault. My terminal is also messed up afterwards. Can anybody help? I'm not quite sure what to do to fix this, or even figure out what is going wrong. Also, does anyone has any other recommendations as to a console-based IM client supporting at least XMPP if I can't get finch working? ___ 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 to "portinstall -P" packages that alter ther names via PKGNAMESUFFIX?
On Wed, 15 Apr 2009 02:24:59 +0300 Panagiotis Christias wrote: > The setup works quite well and has saved us a lot of time and effort. > Currently we are looking for ways to automate as much as possible the > whole process. One of the problems we face is the initial > installation of packages that alter their names, like > sendmail+tls+sasl2+ldap+db46 and openldap-sasl-server. Seems like > there is no obvious way to "portinstall -P" such packages. This is sometimes handled through slave ports e.g. net/cvsup-without-gui. If there aren't too many variations you might create some local slave ports. ___ 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: Samba 3.x build problems with LDAP support
Hi, Erik! I guess the answer lays in the config.log, where it said: idmap_ldap ... static So, it is compiled into Samba. Regards, Timur. On Sat, Apr 11, 2009 at 10:39 PM, Erik Van Benschoten wrote: > Hello, > > Is anyone else experiencing problems building/installing samba32 or samba33? > Either port does not seem to install the idmap_ldap backend. I've tried > uninstalling > everything and then reinstalling from scratch - no luck. The other idmap > backends > (ad, adex, hash, rid & tdb2) are installed fine. > > Thanks, > Erik Van Benschoten > ___ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
