Re: Ports management tools in the base (Was: Re: cvs commit: www/en/projects/ideas ideas.xml)
Quoting Doug Barton [EMAIL PROTECTED] (from Tue, 20 Mar 2007 15:47:25 -0700): Alexander Leidinger wrote: Quoting Rene Ladan [EMAIL PROTECTED] (Tue, 20 Mar 2007 21:20:18 +0100): Not having a /usr/local/lib/compat/pkg is cleaner IMO. It requires you to have all software up-to-date after a library version bump. This is not always desired. Can you explain in more detail when and why that might be the case? What I'm trying to figure out is where the 80/20 line is here. When you need a program which needs a newer lib than installed on a production system, but you don't get a maintenance window to update all other programs which use this lib, then not having the old lib will hurt. When the reason for the library version bump also requires to change some parts in the source of the programs which make use of the lib, you have to update all programs at once. If some programs have bugs in more recent versions which you can't accept in production and when you need to install a program which needs the new lib version, you are busted when you don't have the old lib around. In the same scenario as in the previous paragraph you also depend upon the release cycle of all involved applications. So if not all programs are available in a compatible version, you are busted too. For some libs having old libs is a nightmare (gettext comes to mind, and every other lib which is used in a lot of other libs and programs), but in general it is a good thing to have the possibility to decide on your own if you want to update everything or only a specific subset. Bye, Alexander. -- Q: How many college football players does it take to screw in a lightbulb? A: Only one, but he gets three credits for it. http://www.Leidinger.netAlexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports management tools in the base (Was: Re: cvs commit: www/en/projects/ideas ideas.xml)
On 3/21/07, Alexander Leidinger [EMAIL PROTECTED] wrote: When you need a program which needs a newer lib than installed on a production system, but you don't get a maintenance window to update all other programs which use this lib, then not having the old lib will hurt. When the reason for the library version bump also requires to change some parts in the source of the programs which make use of the lib, you have to update all programs at once. If some programs have bugs in more recent versions which you can't accept in production and when you need to install a program which needs the new lib version, you are busted when you don't have the old lib around. But don't you smell an architectural flaw here (of the ports system) and don't you feel that working around it in a tool in the base system might only mess things up even more?.. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Openssh
Hi I noticed that Openssh port shows in the list of ports that need to be updated to the latest version (4.6), I dont have much experience updating a port but If nobody is working on that, I would really like to give it I try? Thanks Alfredo ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Unfetchable distfiles reminder
Dear porters, This is just a reminder to please periodically check the list of unfetchable distfiles at http://people.freebsd.org/~fenner/portsurvey/ . In particular, the list of ports with no MAINTAINER with distfile problems, which currently has 220 bad ports, is http://people.freebsd.org/~fenner/portsurvey/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. In addition, the list of all ports with any unfetchable distfile is http://people.freebsd.org/~fenner/portsurvey/bad.html if you don't mind coordinating your fixes with the port MAINTAINER. Thanks for your help! Bill distfiles Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports management tools in the base (Was: Re: cvs commit: www/en/projects/ideas ideas.xml)
On 3/21/07, Pav Lucistnik [EMAIL PROTECTED] wrote: Andrew Pantyukhin píše v st 21. 03. 2007 v 11:31 +0300: On 3/21/07, Alexander Leidinger [EMAIL PROTECTED] wrote: When you need a program which needs a newer lib than installed on a production system, but you don't get a maintenance window to update all other programs which use this lib, then not having the old lib will hurt. When the reason for the library version bump also requires to change some parts in the source of the programs which make use of the lib, you have to update all programs at once. If some programs have bugs in more recent versions which you can't accept in production and when you need to install a program which needs the new lib version, you are busted when you don't have the old lib around. But don't you smell an architectural flaw here (of the ports system) and don't you feel that working around it in a tool in the base system might only mess things up even more?.. No I don't see a systematic flaw here. Or you suggest we reset all shmajors everywhere to zero? I would suggest that multiple versions of any port should be allowed to be installed simultaneously - and without the burden of introducing versioned ports. I do not volunteer just yet to propose an outline of a solution to make that possible, but workarounds have a tendency to be tolerated in the long run once introduced into the base system. objformat tool is a nice example of such a workaround. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports management tools in the base (Was: Re: cvs commit: www/en/projects/ideas ideas.xml)
Andrew Pantyukhin píše v st 21. 03. 2007 v 13:55 +0300: On 3/21/07, Pav Lucistnik [EMAIL PROTECTED] wrote: Andrew Pantyukhin píše v st 21. 03. 2007 v 11:31 +0300: On 3/21/07, Alexander Leidinger [EMAIL PROTECTED] wrote: When you need a program which needs a newer lib than installed on a production system, but you don't get a maintenance window to update all other programs which use this lib, then not having the old lib will hurt. When the reason for the library version bump also requires to change some parts in the source of the programs which make use of the lib, you have to update all programs at once. If some programs have bugs in more recent versions which you can't accept in production and when you need to install a program which needs the new lib version, you are busted when you don't have the old lib around. But don't you smell an architectural flaw here (of the ports system) and don't you feel that working around it in a tool in the base system might only mess things up even more?.. No I don't see a systematic flaw here. Or you suggest we reset all shmajors everywhere to zero? I would suggest that multiple versions of any port should be allowed to be installed simultaneously - and without the burden of introducing versioned ports. How would that work? I'm curious. I do not volunteer just yet to propose an outline of a solution to make that possible, but workarounds have a tendency to be tolerated in the long run once introduced into the base system. objformat tool is a nice example of such a workaround. Let's say I prefer a working system now than neatly designed system in 2014. -- Pav Lucistnik [EMAIL PROTECTED] [EMAIL PROTECTED] ... the obese drugged penguin used by Linux. -- Scott Long signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Ports management tools in the base (Was: Re: cvs commit: www/en/projects/ideas ideas.xml)
On 3/21/07, Pav Lucistnik [EMAIL PROTECTED] wrote: Andrew Pantyukhin píše v st 21. 03. 2007 v 13:55 +0300: On 3/21/07, Pav Lucistnik [EMAIL PROTECTED] wrote: Andrew Pantyukhin píše v st 21. 03. 2007 v 11:31 +0300: On 3/21/07, Alexander Leidinger [EMAIL PROTECTED] wrote: When you need a program which needs a newer lib than installed on a production system, but you don't get a maintenance window to update all other programs which use this lib, then not having the old lib will hurt. When the reason for the library version bump also requires to change some parts in the source of the programs which make use of the lib, you have to update all programs at once. If some programs have bugs in more recent versions which you can't accept in production and when you need to install a program which needs the new lib version, you are busted when you don't have the old lib around. But don't you smell an architectural flaw here (of the ports system) and don't you feel that working around it in a tool in the base system might only mess things up even more?.. No I don't see a systematic flaw here. Or you suggest we reset all shmajors everywhere to zero? I would suggest that multiple versions of any port should be allowed to be installed simultaneously - and without the burden of introducing versioned ports. How would that work? I'm curious. Several systems have such a feature. SEPP for one. I do not volunteer just yet to propose an outline of a solution to make that possible, but workarounds have a tendency to be tolerated in the long run once introduced into the base system. objformat tool is a nice example of such a workaround. Let's say I prefer a working system now than neatly designed system in 2014. Will you have figured out how to work around similar problems with all other dependency cases by 2014? There are libraries in interpreted languages, static libs, and just old programs that require old programs to function. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Openssh
Alfredo Perez wrote: Hi I noticed that Openssh port shows in the list of ports that need to be updated to the latest version (4.6), I dont have much experience updating a port but If nobody is working on that, I would really like to give it I try? Thanks Alfredo install portmaster from the ports tree and let it update it for you. its pretty easy ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Openssh
In response to Eric [EMAIL PROTECTED]: Alfredo Perez wrote: Hi I noticed that Openssh port shows in the list of ports that need to be updated to the latest version (4.6), I dont have much experience updating a port but If nobody is working on that, I would really like to give it I try? Thanks Alfredo install portmaster from the ports tree and let it update it for you. its pretty easy I think he's referring to generating a set of diffs and submitting a PR, as the OpenSSH in the ports tree is only 3.6.1 Alfredo: Start by reading The Porter's Handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html Different ports require different levels of expertise to create -- I don't know what you're getting yourself in to with OpenSSH -- it could be easy or hard, but the place to start would be that handbook. If you hit specific problems, post the details of where you get stuck to the list and I'm sure others will help out. -- Bill Moran http://www.potentialtech.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Openssh
Bill Moran wrote: In response to Eric [EMAIL PROTECTED]: Alfredo Perez wrote: Hi I noticed that Openssh port shows in the list of ports that need to be updated to the latest version (4.6), I dont have much experience updating a port but If nobody is working on that, I would really like to give it I try? Thanks Alfredo install portmaster from the ports tree and let it update it for you. its pretty easy I think he's referring to generating a set of diffs and submitting a PR, as the OpenSSH in the ports tree is only 3.6.1 ah, i saw 4.6 and thought of openssh portable. sorry for the noise ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
portupgrade query -- MOVEDError
[EMAIL PROTECTED] /usr/ports]# portupgrade -a /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:119:in `fill': MOVED file format error (PortsDB::MOVEDError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `each' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `open' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:107:in `initialize' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `new' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `setup' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:256:in `init_pkgtools_global' from /usr/local/sbin/portupgrade:519:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize' from /usr/local/sbin/portupgrade:220:in `new' from /usr/local/sbin/portupgrade:220:in `main' from /usr/local/sbin/portupgrade:2084 [EMAIL PROTECTED] /usr/ports]# ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade query -- MOVEDError
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vizion Sent: Wednesday, March 21, 2007 8:04 AM To: [EMAIL PROTECTED] Subject: portupgrade query -- MOVEDError [EMAIL PROTECTED] /usr/ports]# portupgrade -a /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:119:in `fill': MOVED file format error (PortsDB::MOVEDError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `each' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `open' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:107:in `initialize' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `new' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `setup' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:256:in `init_pkgtools_global' from /usr/local/sbin/portupgrade:519:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize' from /usr/local/sbin/portupgrade:220:in `new' from /usr/local/sbin/portupgrade:220:in `main' from /usr/local/sbin/portupgrade:2084 [EMAIL PROTECTED] /usr/ports]# I omitted to say-- what is happening here?? david ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade query -- MOVEDError
try to upgrade ur portupgrade /usr/port/port-mgmt/portupgrade Vizion wrote: [EMAIL PROTECTED] /usr/ports]# portupgrade -a /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:119:in `fill': MOVED file format error (PortsDB::MOVEDError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `each' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `open' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:107:in `initialize' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `new' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `setup' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:256:in `init_pkgtools_global' from /usr/local/sbin/portupgrade:519:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize' from /usr/local/sbin/portupgrade:220:in `new' from /usr/local/sbin/portupgrade:220:in `main' from /usr/local/sbin/portupgrade:2084 [EMAIL PROTECTED] /usr/ports]# ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade query -- MOVEDError
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Ooi Cong Jen Sent: Wednesday, March 21, 2007 8:08 AM To: Vizion Cc: [EMAIL PROTECTED] Subject: Re: portupgrade query -- MOVEDError try to upgrade ur portupgrade /usr/port/port-mgmt/portupgrade Vizion wrote: [EMAIL PROTECTED] /usr/ports]# portupgrade -a /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:119:in `fill': MOVED file format error (PortsDB::MOVEDError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `each' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `open' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:107:in `initialize' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `new' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `setup' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:256:in `init_pkgtools_global' from /usr/local/sbin/portupgrade:519:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize' from /usr/local/sbin/portupgrade:220:in `new' from /usr/local/sbin/portupgrade:220:in `main' from /usr/local/sbin/portupgrade:2084 [EMAIL PROTECTED] /usr/ports]# The error comes from the attempt by portupgrade -a to upgrade /usr/ports/ports-mgt/portgrade. Soame errot is given if you run portupgrade in the ports-mgmt/portsupgrade directory. david david ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Thank you for portmaster
On Tuesday 20 March 2007 06:47 pm, Sticky Bit wrote: first let me thank you for developing such a nice tool! After so long time using portupgrade I gave portmaster a chance to convince me in daily usage. Now I am very happy with this decision and I begin to really like portmaster. One feature I would like to see implemented is a switch 'list only ports that have available updates'. I want to know all affected ports in summary before the builds so I am able to make decisions (i.e. 'portmaster -a' or just 'portmaster port', and think of the 'devel/gettext' update or other huge / long builds like gnome / gtk+ etc.). I am aware of the '-L' switch and the possibility to grep such ports. But this is a bit odd and not very likable. I want a similar output like 'portversion -vL=', i.e. port name along with old and new version numbering but only for ports with a different version available than installed (can also be an older version, think of a manually modified ports tree). Could you please add this small feature? Then I am actually able to do without portupgrade and its other tools. Use the right tool for the job: pkg_version. :) What you want is: pkg_version -vl '' That will list all the installed apps that have updates available in the ports tree. Combine that with a little work using pkg_info -rx appname and pkg_info -Rx appname to see dependencies, and you can determine how to call portmaster. Read the man pages for pkg_info, pkg_add, pkg_version, and pkg_delete, to see all the things you can do with the ports/packages system. Those, combined with portmaster, make for an excellent little ports toolkit. -- Freddie Cash [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade query -- MOVEDError
pkg_deinstall portupgrade and go to /usr/ports/port-mgmt/portupgrade make and make install I tried that and the error message gone. I think something to do with path setting. Vizion wrote: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Ooi Cong Jen Sent: Wednesday, March 21, 2007 8:08 AM To: Vizion Cc: [EMAIL PROTECTED] Subject: Re: portupgrade query -- MOVEDError try to upgrade ur portupgrade /usr/port/port-mgmt/portupgrade Vizion wrote: [EMAIL PROTECTED] /usr/ports]# portupgrade -a /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:119:in `fill': MOVED file format error (PortsDB::MOVEDError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `each' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `open' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:107:in `initialize' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `new' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `setup' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:256:in `init_pkgtools_global' from /usr/local/sbin/portupgrade:519:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize' from /usr/local/sbin/portupgrade:220:in `new' from /usr/local/sbin/portupgrade:220:in `main' from /usr/local/sbin/portupgrade:2084 [EMAIL PROTECTED] /usr/ports]# The error comes from the attempt by portupgrade -a to upgrade /usr/ports/ports-mgt/portgrade. Soame errot is given if you run portupgrade in the ports-mgmt/portsupgrade directory. david david ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade query -- MOVEDError
Vizion wrote: The error comes from the attempt by portupgrade -a to upgrade /usr/ports/ports-mgt/portgrade. Soame errot is given if you run portupgrade in the ports-mgmt/portsupgrade directory. The error is caused by a syntax error in the file /usr/ports/MOVED Change the last line from: lang/xotcl-thread|2007-03-21|Not longer needed to: lang/xotcl-thread||2007-03-21|Not longer needed ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Portupgrade failed
Hallo, error with portupgrade, what I have to do (I need help please) portsdb -u portsdb: MOVED file format error portupgrade -a /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:119:in `fill': MOVED file format error (PortsDB::MOVEDError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `each' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `open' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:107:in `initialize' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `new' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `setup' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:256:in `init_pkgtools_global' from /usr/local/sbin/portupgrade:519:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize' from /usr/local/sbin/portupgrade:220:in `new' from /usr/local/sbin/portupgrade:220:in `main' from /usr/local/sbin/portupgrade:2084 Thanks Joachim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade failed
2007/3/21, Joachim Bethke [EMAIL PROTECTED]: Hallo, error with portupgrade, what I have to do (I need help please) portsdb -u portsdb: MOVED file format error portupgrade -a /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:119:in `fill': MOVED file format error (PortsDB::MOVEDError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `each' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `open' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:107:in `initialize' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `new' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `setup' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:256:in `init_pkgtools_global' from /usr/local/sbin/portupgrade:519:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize' from /usr/local/sbin/portupgrade:220:in `new' from /usr/local/sbin/portupgrade:220:in `main' from /usr/local/sbin/portupgrade:2084 Thanks Joachim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] Please update your MOVED file and try again, it was fixed some hour ago Greetings ACM ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portupgrade query -- MOVEDError
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [LoN]Kamikaze Sent: Wednesday, March 21, 2007 9:10 AM To: freebsd-ports@freebsd.org Subject: Re: portupgrade query -- MOVEDError Vizion wrote: The error comes from the attempt by portupgrade -a to upgrade /usr/ports/ports-mgt/portgrade. Soame errot is given if you run portupgrade in the ports-mgmt/portsupgrade directory. The error is caused by a syntax error in the file /usr/ports/MOVED Change the last line from: lang/xotcl-thread|2007-03-21|Not longer needed to: lang/xotcl-thread||2007-03-21|Not longer needed That fixed it -- thank you SDavid ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade failed
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joachim Bethke Sent: Wednesday, March 21, 2007 9:20 AM To: freebsd-ports@freebsd.org Subject: Portupgrade failed Hallo, error with portupgrade, what I have to do (I need help please) portsdb -u portsdb: MOVED file format error portupgrade -a /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:119:in `fill': MOVED file format error (PortsDB::MOVEDError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `each' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `open' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:107:in `initialize' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `new' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `setup' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:256:in `init_pkgtools_global' from /usr/local/sbin/portupgrade:519:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize' from /usr/local/sbin/portupgrade:220:in `new' from /usr/local/sbin/portupgrade:220:in `main' from /usr/local/sbin/portupgrade:2084 Thanks Joachim from similar thread: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [LoN]Kamikaze Sent: Wednesday, March 21, 2007 9:10 AM To: freebsd-ports@freebsd.org Subject: Re: portupgrade query -- MOVEDError Vizion wrote: The error comes from the attempt by portupgrade -a to upgrade /usr/ports/ports-mgt/portgrade. Soame errot is given if you run portupgrade in the ports-mgmt/portsupgrade directory. The error is caused by a syntax error in the file /usr/ports/MOVED Change the last line from: lang/xotcl-thread|2007-03-21|Not longer needed to: lang/xotcl-thread||2007-03-21|Not longer needed That fixed it -- thank you SDavid ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade failed
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joachim Bethke Sent: Wednesday, March 21, 2007 9:20 AM To: freebsd-ports@freebsd.org Subject: Portupgrade failed Hallo, error with portupgrade, what I have to do (I need help please) portsdb -u portsdb: MOVED file format error portupgrade -a /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:119:in `fill': MOVED file format error (PortsDB::MOVEDError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `each' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `open' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:107:in `initialize' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `new' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `setup' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:256:in `init_pkgtools_global' from /usr/local/sbin/portupgrade:519:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize' from /usr/local/sbin/portupgrade:220:in `new' from /usr/local/sbin/portupgrade:220:in `main' from /usr/local/sbin/portupgrade:2084 Thanks Joachim from similar thread: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [LoN]Kamikaze Sent: Wednesday, March 21, 2007 9:10 AM To: freebsd-ports@freebsd.org Subject: Re: portupgrade query -- MOVEDError Vizion wrote: The error comes from the attempt by portupgrade -a to upgrade /usr/ports/ports-mgt/portgrade. Soame errot is given if you run portupgrade in the ports-mgmt/portsupgrade directory. The error is caused by a syntax error in the file /usr/ports/MOVED Change the last line from: lang/xotcl-thread|2007-03-21|Not longer needed to: lang/xotcl-thread||2007-03-21|Not longer needed That fixed it -- thank you SDavid ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
mail/maildrop marked as broken
As title for information New today: portupgrade -a reports: FAM system mismatch: gamin is imstalled and desired FAM system is fam david ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
pandoc not fetchable?
According to the port survey, http://people.freebsd.org/~fenner/portsurvey/textproc.html#pandoc, the distfile for the port I maintain (textproc/pandoc) is not fetchable: http://pandoc.googlecode.com/files/pandoc-0.3.tar.gz: 404 Not Found (Last OK result NEVER [checked 12 times since Tue Feb 13 I can't understand why. The file is there on the server, I can fetch it from that URL using wget, and when I install the port, it fetches the file just fine from http://pandoc.googlecode.com. So why is portsurvey not finding it? I'm new at FreeBSD, so maybe there's something simple I'm missing. Any help would be appreciated. John ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD ports you maintain which are out of date
Port| Current version | New version print/ghostscript-afpl-nox11| 8.54| 8.56 I believe the Current version to be the latest and there is no 8.56. print/ghostscript-gnu-nox11 | 7.07| 8.56 I believe the Current version to be the latest and there is no 8.56. print/ghostscript-gpl-nox11 | 8.15| 8.56 That looks correct. What's going on here? http://sourceforge.net/project/showfiles.php?group_id=1897 security/dropbear | 0.49| 0.255 Huh? http://matt.ucc.asn.au/dropbear/dropbear.html -=EPS=- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [EMAIL PROTECTED]: linuxdcpp-0.0.1.20070206 failed on amd64 7]
On Tue, 20 Mar 2007 15:21:39 -0500, Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Mar 20, 2007 at 02:55:09PM -0500, Jeremy Messenger wrote: On Tue, 20 Mar 2007 12:16:22 -0500, Kris Kennaway [EMAIL PROTECTED] wrote: Dear Maintainer, As you may know, in the near future FreeBSD 7.x will be switching from the gcc 3.4 compiler to gcc 4.x. Unfortunately your port fails to build with the new compiler; see the log below. To ease the disruption to users and to avoid further work later on, can you please work (with the upstream developers if necessary) on fixing this error? In many cases it requires only simple code changes, and these may already have been submitted to the developers by other projects (thesedays many Linux distributions use gcc 4.1, so chances are they have fixed the error already), or the patches may be found in their package repositories. You should be able to reproduce it yourself simply by installing the lang/gcc41 port and then setting the variables CC=/usr/local/bin/gcc41 CXX=/usr/local/bin/g++41 in your environment (Note: some ports do not respect these variables currently, but this is another bug that should be fixed). I can't reproduce it. Any idea why I can't? Thanks. # pkg_info | grep gcc gcc-4.1.3_20070312 GNU Compiler Collection 4.1 # make -DGCC4 === Extracting for linuxdcpp-0.0.1.20070206 = MD5 Checksum OK for linuxdcpp-0.0.1.20070206.tar.bz2. = SHA256 Checksum OK for linuxdcpp-0.0.1.20070206.tar.bz2. [...] === Building for linuxdcpp-0.0.1.20070206 scons: Reading SConscript files ... Checking for /usr/local/bin/g++41 = 3.4...(cached) yes [...] scons: Building targets ... /usr/local/bin/g++41 -o build/client/AdcCommand.o -c -O2 -fno-strict-aliasing -pipe -g -I. -I/usr/local/include -I. -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DICONV_CONST=const -D_DATADIR='/usr/local/share' client/AdcCommand.cpp /usr/local/bin/g++41 -o build/client/AdcHub.o -c -O2 -fno-strict-aliasing -pipe -g -I. -I/usr/local/include -I. -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DICONV_CONST=const -D_DATADIR='/usr/local/share' client/AdcHub.cpp /usr/local/bin/g++41 -o build/client/ADLSearch.o -c -O2 -fno-strict-aliasing -pipe -g -I. -I/usr/local/include -I. -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DICONV_CONST=const -D_DATADIR='/usr/local/share' client/ADLSearch.cpp [...goes on without failure...] Is this on amd64? No, it's 6.2-STABLE i386. I guess, I can mark it as broken on 7.x amd64. Cheers, Mezz Kris -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pandoc not fetchable?
This happens with anything hosted at googlecode.com. E.g. net-im/naim has the same problem. -=EPS=- ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mail/maildrop marked as broken
From: Vizion [EMAIL PROTECTED] Subject: mail/maildrop marked as broken Date: Wed, 21 Mar 2007 11:33:59 -0700 As title for information New today: portupgrade -a reports: FAM system mismatch: gamin is imstalled and desired FAM system is fam AFAIK Courier products work only with fam and not with gamin. But I not certain this is still the case now. Does anyone know if latest gamin is compatible with Courier products? --- KIMURA Yasuhiro ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Portupgrade failed
Vizion schrieb: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Joachim Bethke Sent: Wednesday, March 21, 2007 9:20 AM To: freebsd-ports@freebsd.org Subject: Portupgrade failed Hallo, error with portupgrade, what I have to do (I need help please) portsdb -u portsdb: MOVED file format error portupgrade -a /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:119:in `fill': MOVED file format error (PortsDB::MOVEDError) from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `each' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:113:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `open' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:112:in `fill' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:107:in `initialize' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `new' from /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:182:in `setup' from /usr/local/lib/ruby/site_ruby/1.8/pkgtools.rb:256:in `init_pkgtools_global' from /usr/local/sbin/portupgrade:519:in `main' from /usr/local/lib/ruby/1.8/optparse.rb:755:in `initialize' from /usr/local/sbin/portupgrade:220:in `new' from /usr/local/sbin/portupgrade:220:in `main' from /usr/local/sbin/portupgrade:2084 Thanks Joachim from similar thread: -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [LoN]Kamikaze Sent: Wednesday, March 21, 2007 9:10 AM To: freebsd-ports@freebsd.org Subject: Re: portupgrade query -- MOVEDError Vizion wrote: The error comes from the attempt by portupgrade -a to upgrade /usr/ports/ports-mgt/portgrade. Soame errot is given if you run portupgrade in the ports-mgmt/portsupgrade directory. The error is caused by a syntax error in the file /usr/ports/MOVED Change the last line from: lang/xotcl-thread|2007-03-21|Not longer needed to: lang/xotcl-thread||2007-03-21|Not longer needed That fixed it -- thank you SDavid Hallo, thanks for the immediately help ! The Problem was solved. Joachim ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Thank you for portmaster
Read the man pages for pkg_info, pkg_add, pkg_version, and pkg_delete, to see all the things you can do with the ports/packages system. Those, combined with portmaster, make for an excellent little ports toolkit. I am using FreeBSD for several years. I really know these tools very well and I already know what I want. They are part of my daily usage. So no help needed. ;-) Maybe you did not understand my intention. It is not a matter of what can be done with other tools but what can be done with portmaster. It was only a feature suggestion to improve portmaster not a request for help. Hope that makes it clear ... -- Kind regards, Sticky Bit *** True standards compliant plain text emails preferred. *** ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Thank you for portmaster
On Wednesday 21 March 2007 01:07 pm, Sticky Bit wrote: Read the man pages for pkg_info, pkg_add, pkg_version, and pkg_delete, to see all the things you can do with the ports/packages system. Those, combined with portmaster, make for an excellent little ports toolkit. I am using FreeBSD for several years. I really know these tools very well and I already know what I want. They are part of my daily usage. So no help needed. ;-) Maybe you did not understand my intention. It is not a matter of what can be done with other tools but what can be done with portmaster. It was only a feature suggestion to improve portmaster not a request for help. Hope that makes it clear ... Ah, but the Unix way is to use a handful of small single-purpose tools, not create swiss-army-knife-style tools that each try to do everything. :) Hence, why you should use pkg_add to install packages, pkg_info to get information on installed packages, pkg_version to see which installed packages have updates available, and portmaster to update installed packages. :) Personally, I'd prefer to have -L removed from portmaster completely. Or, at least the search for updates part of it. :D -- Freddie Cash [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Openssh
Yes Bill, you are right. With some help, I already update a port (imgseek) Do I need to be the maintainer of Openssh to submit a PR with a diff? Alfredo Bill Moran [EMAIL PROTECTED] wrote: In response to Eric : Alfredo Perez wrote: Hi I noticed that Openssh port shows in the list of ports that need to be updated to the latest version (4.6), I dont have much experience updating a port but If nobody is working on that, I would really like to give it I try? Thanks Alfredo install portmaster from the ports tree and let it update it for you. its pretty easy I think he's referring to generating a set of diffs and submitting a PR, as the OpenSSH in the ports tree is only 3.6.1 Alfredo: Start by reading The Porter's Handbook: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html Different ports require different levels of expertise to create -- I don't know what you're getting yourself in to with OpenSSH -- it could be easy or hard, but the place to start would be that handbook. If you hit specific problems, post the details of where you get stuck to the list and I'm sure others will help out. -- Bill Moran http://www.potentialtech.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [EMAIL PROTECTED]: linuxdcpp-0.0.1.20070206 failed on amd64 7]
On Wed, Mar 21, 2007 at 02:51:31PM -0500, Jeremy Messenger wrote: On Tue, 20 Mar 2007 15:21:39 -0500, Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Mar 20, 2007 at 02:55:09PM -0500, Jeremy Messenger wrote: On Tue, 20 Mar 2007 12:16:22 -0500, Kris Kennaway [EMAIL PROTECTED] wrote: Dear Maintainer, As you may know, in the near future FreeBSD 7.x will be switching from the gcc 3.4 compiler to gcc 4.x. Unfortunately your port fails to build with the new compiler; see the log below. To ease the disruption to users and to avoid further work later on, can you please work (with the upstream developers if necessary) on fixing this error? In many cases it requires only simple code changes, and these may already have been submitted to the developers by other projects (thesedays many Linux distributions use gcc 4.1, so chances are they have fixed the error already), or the patches may be found in their package repositories. You should be able to reproduce it yourself simply by installing the lang/gcc41 port and then setting the variables CC=/usr/local/bin/gcc41 CXX=/usr/local/bin/g++41 in your environment (Note: some ports do not respect these variables currently, but this is another bug that should be fixed). I can't reproduce it. Any idea why I can't? Thanks. # pkg_info | grep gcc gcc-4.1.3_20070312 GNU Compiler Collection 4.1 # make -DGCC4 === Extracting for linuxdcpp-0.0.1.20070206 = MD5 Checksum OK for linuxdcpp-0.0.1.20070206.tar.bz2. = SHA256 Checksum OK for linuxdcpp-0.0.1.20070206.tar.bz2. [...] === Building for linuxdcpp-0.0.1.20070206 scons: Reading SConscript files ... Checking for /usr/local/bin/g++41 = 3.4...(cached) yes [...] scons: Building targets ... /usr/local/bin/g++41 -o build/client/AdcCommand.o -c -O2 -fno-strict-aliasing -pipe -g -I. -I/usr/local/include -I. -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DICONV_CONST=const -D_DATADIR='/usr/local/share' client/AdcCommand.cpp /usr/local/bin/g++41 -o build/client/AdcHub.o -c -O2 -fno-strict-aliasing -pipe -g -I. -I/usr/local/include -I. -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DICONV_CONST=const -D_DATADIR='/usr/local/share' client/AdcHub.cpp /usr/local/bin/g++41 -o build/client/ADLSearch.o -c -O2 -fno-strict-aliasing -pipe -g -I. -I/usr/local/include -I. -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DICONV_CONST=const -D_DATADIR='/usr/local/share' client/ADLSearch.cpp [...goes on without failure...] Is this on amd64? No, it's 6.2-STABLE i386. I guess, I can mark it as broken on 7.x amd64. Well it's only broken with the non-imported compiler, so if you're going to go the mark broken route then please wait for the import. And also talk to the developers of course. Kris ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: mail/maildrop marked as broken
On Wednesday 21 March 2007 21:13, KIMURA Yasuhiro wrote: From: Vizion [EMAIL PROTECTED] Subject: mail/maildrop marked as broken Date: Wed, 21 Mar 2007 11:33:59 -0700 As title for information New today: portupgrade -a reports: FAM system mismatch: gamin is imstalled and desired FAM system is fam AFAIK Courier products work only with fam and not with gamin. But I not certain this is still the case now. Does anyone know if latest gamin is compatible with Courier products? --- KIMURA Yasuhiro This is part of installed packages on one from my servers: pkg_info apache-2.2.4Version 2.2 of Apache web server with prefork MPM. arc-5.21o_1 Create extract files from DOS .ARC files arj-3.10.22 Open-source ARJ autoconf-2.53_3 Automatically configure source code on many Un*x platforms autoconf-2.59_2 Automatically configure source code on many Un*x platforms automake-1.5_2,1GNU Standards-compliant Makefile generator (1.5) automake-1.9.6 GNU Standards-compliant Makefile generator (1.9) clamav-0.90_3 Command line virus scanner written entirely in C clamcour-0.3.8 ClamAV courier filter courier-0.54.0 Courier SMTP IMAP POP3 HTTP mail server suite courier-authlib-base-0.59.1 Courier authentication library base courier-authlib-userdb-0.59.1 Userdb support for the Courier authentication library courier-pythonfilter-0.18 Framework for courier filter development in python curl-7.16.1 Non-interactive tool to get files from FTP, GOPHER, HTTP(S) docbook-1.3 Meta-port for the different versions of the DocBook DTD docbook-241_2 V2.4.1 of the DocBook DTD, designed for technical documenta docbook-3.0_2 V3.0 of the DocBook DTD, designed for technical documentati docbook-3.1_2 V3.1 of the DocBook DTD, designed for technical documentati docbook-4.0_2 V4.0 of the DocBook DTD, designed for technical documentati docbook-4.1_2 V4.1 of the DocBook DTD, designed for technical documentati docbook-xml-4.2_1 XML version of the DocBook DTD expat-2.0.0_1 XML 1.0 parser written in C gamin-0.1.7_2 A file and directory monitoring system And it works well. So yes, courier could be used with gamin. And if full courier suite works well, it could work partially, too. Regards, Milan -- No need to mail me directly. Just reply to mailing list, please. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Eye of Gnome error after upgrading to 2.18
On Wed, 21 Mar 2007 00:55:24 -0500, Indigo 23 [EMAIL PROTECTED] wrote: After upgrading to Gnome 2.18 from 2.16 [in which I mostly used packages from marcuscom], I receive the following error when trying to open an image using Eye of Gnome 2.18 (eog-2.18.0.1): Couldn't load image 'gnome-failed.jpg'. Unable to load image-loading module: /usr/X11R6/lib/gtk-2.0/2.4.0/loaders/libpixbufloader-jpeg.so: Cannot open /usr/X11R6/lib/gtk-2.0/2.4.0/loaders/libpixbufloader-jpeg.so and in the Terminal I get the following: (eog:66783): Gtk-WARNING **: Unable to locate theme engine in module_path: murrine, I recompiled the murrine/murrina themes after upgrading (just in case), and I am running 6.2. Anyone have any idea what's wrong and how it can be fixed? I am not sure, but it looks like you have not follow in /usr/ports/UPDATING (20061014) correct. Cheers, Mezz Thanks. -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Openssh
On Wed, Mar 21, 2007 at 04:51:08PM -0400, Alfredo Perez wrote: Do I need to be the maintainer of Openssh to submit a PR with a diff? No. We will forward your PR to the maintainer. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: A review of different port management tools : analysis for Google SoC project
Gary Kline píše v út 20. 03. 2007 v 21:05 -0800: How about this idea for integrating into a new ports/package project: say for people with a fast I686 who wanted -O3 and -pipe and wanted his packages built remotely rather than his own computer. Would be be posssible to build a package, custom (according to one's /etc/make.conf) on FreeBSD's servers, then fetch the *tgz package back? Kernels, and worlds would reside on the remote server for only a few hours before being automatically cleansed. This would be super for everything from a i486-166MHz with 32Megs that was serving mail *only*, a slow to moderate i686, or even an AMD 2800. Building locally is sometimes the only way. But if users have slower servers and there are no current packages (i386), why not let the builds be queued? Just so you know, existing FreeBSD's servers, as you put it, are Pentium III blades clocked at 700 MHz. And we tend to keep them rather busy. -- Pav Lucistnik [EMAIL PROTECTED] [EMAIL PROTECTED] Why do we need a film of Lord of the Rings when we have the book? Because watching a cg enhanced Legolas fire a flaming arrow into the heart of a warg is cool? - [EMAIL PROTECTED] in rec.games.roguelike.angband signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: [EMAIL PROTECTED]: linuxdcpp-0.0.1.20070206 failed on amd64 7]
Kris Kennaway píše v st 21. 03. 2007 v 16:53 -0400: On Wed, Mar 21, 2007 at 02:51:31PM -0500, Jeremy Messenger wrote: On Tue, 20 Mar 2007 15:21:39 -0500, Kris Kennaway [EMAIL PROTECTED] wrote: On Tue, Mar 20, 2007 at 02:55:09PM -0500, Jeremy Messenger wrote: On Tue, 20 Mar 2007 12:16:22 -0500, Kris Kennaway [EMAIL PROTECTED] wrote: Dear Maintainer, As you may know, in the near future FreeBSD 7.x will be switching from the gcc 3.4 compiler to gcc 4.x. Unfortunately your port fails to build with the new compiler; see the log below. To ease the disruption to users and to avoid further work later on, can you please work (with the upstream developers if necessary) on fixing this error? In many cases it requires only simple code changes, and these may already have been submitted to the developers by other projects (thesedays many Linux distributions use gcc 4.1, so chances are they have fixed the error already), or the patches may be found in their package repositories. You should be able to reproduce it yourself simply by installing the lang/gcc41 port and then setting the variables CC=/usr/local/bin/gcc41 CXX=/usr/local/bin/g++41 in your environment (Note: some ports do not respect these variables currently, but this is another bug that should be fixed). I can't reproduce it. Any idea why I can't? Thanks. # pkg_info | grep gcc gcc-4.1.3_20070312 GNU Compiler Collection 4.1 # make -DGCC4 === Extracting for linuxdcpp-0.0.1.20070206 = MD5 Checksum OK for linuxdcpp-0.0.1.20070206.tar.bz2. = SHA256 Checksum OK for linuxdcpp-0.0.1.20070206.tar.bz2. [...] === Building for linuxdcpp-0.0.1.20070206 scons: Reading SConscript files ... Checking for /usr/local/bin/g++41 = 3.4...(cached) yes [...] scons: Building targets ... /usr/local/bin/g++41 -o build/client/AdcCommand.o -c -O2 -fno-strict-aliasing -pipe -g -I. -I/usr/local/include -I. -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DICONV_CONST=const -D_DATADIR='/usr/local/share' client/AdcCommand.cpp /usr/local/bin/g++41 -o build/client/AdcHub.o -c -O2 -fno-strict-aliasing -pipe -g -I. -I/usr/local/include -I. -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DICONV_CONST=const -D_DATADIR='/usr/local/share' client/AdcHub.cpp /usr/local/bin/g++41 -o build/client/ADLSearch.o -c -O2 -fno-strict-aliasing -pipe -g -I. -I/usr/local/include -I. -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -DICONV_CONST=const -D_DATADIR='/usr/local/share' client/ADLSearch.cpp [...goes on without failure...] Is this on amd64? No, it's 6.2-STABLE i386. I guess, I can mark it as broken on 7.x amd64. Well it's only broken with the non-imported compiler, so if you're going to go the mark broken route then please wait for the import. And also talk to the developers of course. I just tried, and it build fine on amd64-6 with gcc41. -- Pav Lucistnik [EMAIL PROTECTED] [EMAIL PROTECTED] Knight: We shall say Ny! again to you if you do not appease us. Arthur: All right. What do you want? Knight: We want... a shruberry! signature.asc Description: Toto je digitálně podepsaná část zprávy
Re: Openssh
That is the thing, the port does not have a maintainer Mark Linimon [EMAIL PROTECTED] wrote: On Wed, Mar 21, 2007 at 04:51:08PM -0400, Alfredo Perez wrote: Do I need to be the maintainer of Openssh to submit a PR with a diff? No. We will forward your PR to the maintainer. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Eye of Gnome error after upgrading to 2.18
On 3/21/07, Jeremy Messenger [EMAIL PROTECTED] wrote: On Wed, 21 Mar 2007 00:55:24 -0500, Indigo 23 [EMAIL PROTECTED] wrote: After upgrading to Gnome 2.18 from 2.16 [in which I mostly used packages from marcuscom], I receive the following error when trying to open an image using Eye of Gnome 2.18 (eog-2.18.0.1): Couldn't load image 'gnome-failed.jpg'. Unable to load image-loading module: /usr/X11R6/lib/gtk-2.0/2.4.0/loaders/libpixbufloader-jpeg.so: Cannot open /usr/X11R6/lib/gtk-2.0/2.4.0/loaders/libpixbufloader-jpeg.so and in the Terminal I get the following: (eog:66783): Gtk-WARNING **: Unable to locate theme engine in module_path: murrine, I recompiled the murrine/murrina themes after upgrading (just in case), and I am running 6.2. Anyone have any idea what's wrong and how it can be fixed? I am not sure, but it looks like you have not follow in /usr/ports/UPDATING (20061014) correct. Cheers, Mezz I did follow what was in there, but there is still some package relying on that old path for some reason and I cannot figure out which one it is. Is there a way to determine which port is causing the problem (i.e. still looking for old gtk libraries)? For the time being, I have a little workaround implemented, but I'd rather fix the problem directly. Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
