py-logilab-common fails with python 2.5
I get this error when upgrading devel/py-logilab-common after updating python to 2.5 : ===>>> Port to upgrade: py24-logilab-common-0.15.0 ===>>> Port directory: /usr/ports/devel/py-logilab-common ===>>> Launching 'make checksum' for devel/py-logilab-common in background ===>>> Gathering dependency list for devel/py-logilab-common from ports ===>>> Starting dependency check ===>>> Dependency check complete for devel/py-logilab-common ===> Cleaning for py25-logilab-common-0.15.0 ===> Extracting for py25-logilab-common-0.15.0 => MD5 Checksum OK for common-0.15.0.tar.gz. => SHA256 Checksum OK for common-0.15.0.tar.gz. /usr/bin/touch /usr/ports/devel/py-logilab-common/work/common-0.15.0/test/__init__.py ===> Patching for py25-logilab-common-0.15.0 ===> py25-logilab-common-0.15.0 depends on file: /usr/local/bin/python - found===> Configuring for py25-logilab-common-0.15.0 File "setup.py", line 22 from __future__ import nested_scopes SyntaxError: from __future__ imports must occur at the beginning of the file *** Error code 1 Stop in /usr/ports/devel/py-logilab-common. ===>>> make failed for devel/py-logilab-common ===>>> Aborting update ===>>> Update for py24-logilab-common-0.15.0 failed ===>>> Aborting update This looks to me as if the source itself is not yet python 2.5 proof. Regards, Rene -- GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) "It won't fit on the line." -- me, 2001 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: py-logilab-common fails with python 2.5
On Fri, Oct 13, 2006 at 10:40:58AM +0200, Rene Ladan wrote: > I get this error when upgrading devel/py-logilab-common after updating > python to 2.5 : > > ===>>> Port to upgrade: py24-logilab-common-0.15.0 > ===>>> Port directory: /usr/ports/devel/py-logilab-common > ===>>> Launching 'make checksum' for devel/py-logilab-common in background > ===>>> Gathering dependency list for devel/py-logilab-common from ports > ===>>> Starting dependency check > ===>>> Dependency check complete for devel/py-logilab-common > > ===> Cleaning for py25-logilab-common-0.15.0 > ===> Extracting for py25-logilab-common-0.15.0 > => MD5 Checksum OK for common-0.15.0.tar.gz. > => SHA256 Checksum OK for common-0.15.0.tar.gz. > /usr/bin/touch > /usr/ports/devel/py-logilab-common/work/common-0.15.0/test/__init__.py > ===> Patching for py25-logilab-common-0.15.0 > ===> py25-logilab-common-0.15.0 depends on file: /usr/local/bin/python > - found===> Configuring for py25-logilab-common-0.15.0 > File "setup.py", line 22 > from __future__ import nested_scopes > SyntaxError: from __future__ imports must occur at the beginning of the file > *** Error code 1 > > Stop in /usr/ports/devel/py-logilab-common. > Due to this sort of errors, lang/python port just downgraded to 2.4. Sorry for the situation but you'd better to downgrade the python port. 2.5 will be back after this 6.2 ports freeze. Hye-Shik ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: man hier? -- FreeBSD Port: sysutils/fusefs-kmod
On Thu, 2006-10-12 at 18:33 +0200, martinko wrote: > Hello, > > I wonder what is the reasoning behind fusefs-kmod port way of dealing > with kernel module(s). > I remember iwi ports putting their modules into /boot/modules and then > one only had to edit /boot/loader.conf[.local] > Now fusefs-kmod creates new directory /usr/local/modules where it puts > its module, then it optionally edit /etc/sysctl.conf to modify > kern.module_path and rc.conf to run /usr/local/etc/rc.d/fusefs script. > Is all of this really necessary and why please ?? It makes the port/package PREFIX-clean. I could have done that for intel firmware ports but I thought it would be too painful for the end-user. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: This is a digitally signed message part
aolserver nsthreadtest fails / aborts ...
Just found this while working on a clients site, and figured I'd mention it ... Aolserver4 has a program called 'nsthreadtest' that you can run from the command line, that aborts part way through: pthread: join 9 = 9 nsthreads: pthread_join failed in Ns_ThreadJoin: Invalid argument Abort (core dumped) It dumps core, with a quick trace showing: (gdb) where #0 0x000800b4781c in pthread_testcancel () from /usr/lib/libpthread.so.2 #1 0x000800b35543 in sigaction () from /usr/lib/libpthread.so.2 #2 0x000800b37062 in sigaction () from /usr/lib/libpthread.so.2 #3 0x000800b30d56 in pthread_kill () from /usr/lib/libpthread.so.2 #4 0x000800b305d3 in raise () from /usr/lib/libpthread.so.2 #5 0x000800d1696d in abort () from /lib/libc.so.6 #6 0x0008007b1cb8 in Tcl_PanicVA () from /usr/local/lib/libtcl84.so.1 #7 0x0008007b1d4d in Tcl_Panic () from /usr/local/lib/libtcl84.so.1 #8 0x000800630a65 in NsThreadFatal () from /usr/local/aolserver/lib/libnsthread.so #9 0x000800632835 in Ns_ThreadJoin () from /usr/local/aolserver/lib/libnsthread.so #10 0x00402868 in main () Don't know if its anything to be concerned about, or just something badly programmed within nsthreadtest, but figured I'd point it out ... if I can provide more details just to confirm it isn't an "OS problem", let me know ... Marc G. Fournier Hub.Org Networking Services (http://www.hub.org) Email . [EMAIL PROTECTED] MSN . [EMAIL PROTECTED] Yahoo . yscrappy Skype: hub.orgICQ . 7615664 pgpupOOLK5d8S.pgp Description: PGP signature
[PATCH] format violation in /lang/f2c fixed
Hi list, I fixed this error which occurs when installing /lang/f2c via ports: # portinstall f2c [Updating the pkgdb in /var/db/pkg ... - 254 packages found (-0 +3) ... done] ---> Installing 'f2c-20060506' from a port (lang/f2c) ---> Building '/usr/ports/lang/f2c' ===> Cleaning for unzip-5.52_2 ===> Cleaning for gmake-3.81_1 ===> Cleaning for gettext-0.14.5_2 ===> Cleaning for libtool-1.5.22_2 ===> Cleaning for libiconv-1.9.2_2 ===> Cleaning for f2c-20060506 ===> Vulnerability check disabled, database not found ===> Extracting for f2c-20060506 => MD5 Checksum OK for f2c-20060506/f2c.tar. => SHA256 Checksum OK for f2c-20060506/f2c.tar. ===> f2c-20060506 depends on file: /usr/local/bin/unzip - found cd /usr/ports/lang/f2c/work/f2c && /usr/bin/find . -name "*.gz" | /usr/bin/xargs /usr/bin/gunzip -f gunzip: ./.master.gz: invalid compressed data--format violated *** Error code 1 Stop in /usr/ports/lang/f2c. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall.7170.0 env make ** Fix the problem and try again. ** Listing the failed packages (*:skipped / !:failed) ! lang/f2c (unknown build error) ---> Packages processed: 0 done, 0 ignored, 0 skipped and 1 failed # .master.gz in /usr/ports/lang/f2c/work/f2c was violated: I couldn't use gunzip on my FreeBSD-box to extract it. I tried gunzip on a Solaris 10 machine which succeeded[0]. Anyway: I created a new .master with the exact same content, gzipped that, patched distinfo (new checksums and filesize), copied the new f2c.tar to /usr/ports/distfiles/f2c-20060506 and all was well :) The new f2c.tar and distinfo are available at http://www.familie-ost.info/~pj/FreeBSD/patches.html I don't intend to host the files forever, I think four weeks should be enough to test and merge this changes into the ports-tree. :) I tested it with FreeBSD 6.2-PRERELEASE (last updated Fri Oct 6 17:15:26 CEST 2006) and it installed without errors. :) Greetings, Philipp P.S.: Please CC me in your answer as I'm not subscribed to the list. Thanks :) [0] Some numbers: Solaris: $ gunzip -V gunzip 1.3.3-patch.1 (2002-03-08) [copyright and license information snipped] $ uname -rsm SunOS 5.10 sun4u FreeBSD: $ gunzip -V gunzip 1.2.4 (18 Aug 93) Compilation options: DIRENT UTIME STDC_HEADERS HAVE_UNISTD_H ASMV $ uname -rsm FreeBSD 6.2-PRERELEASE i386 -- www.familie-ost.info/~pj ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH] format violation in /lang/f2c fixed
Hi, Philipp, Philipp Ost wrote: > Hi list, > > I fixed this error which occurs when installing /lang/f2c via ports: Thanks. We are aware of this issue, but this is more a gzip regression rather than a wrong distfile. A possible workaround for this would be to use minigzip instead of gunzip. I have proposed a potential long term solution by replacing GNU gzip with BSD gzip, as discussed in recent -current mailing list. Cheers, -- Xin LI <[EMAIL PROTECTED]> http://www.delphij.net/ FreeBSD - The Power to Serve! signature.asc Description: OpenPGP digital signature
What is this?
Hi One thing i do not understand: ,[ ports/UPDATING ] | 20061009: | ^ (LOO AT THIS!) | AFFECTS: users of any ports using Python | AUTHOR: [EMAIL PROTECTED] | | After upgrading of lang/python, you must rebuild all its consumer | ports to make them get ready to Python 2.5. | ^^ | To do this, you will need to: | pkgdb -uf && cd /usr/ports/lang/python && make upgrade-site-packages ` vs: ,[ ports/lang/python/Makefile ] | ports/lang/python/Makefile,v 1.157 2006/10/13 |^^ | PORTNAME= python | PORTVERSION= 2.4.3 | ^ ` finally: 1) In ports/UPDATING is python 2.5 mentioned on 9th october. 2) in the makefile of lang/python is the perversion 2.4.3 on 13th october So, what is now correct? How should i deal with the stale dependencies? Heino ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH] format violation in /lang/f2c fixed
LI Xin wrote: Hi, Philipp, Philipp Ost wrote: Hi list, I fixed this error which occurs when installing /lang/f2c via ports: Thanks. We are aware of this issue, but this is more a gzip regression rather than a wrong distfile. I didn't know that. In fact, I was pissed of that I couldn't install f2c. :) The distfile was only changed because I changed the f2c.tar-archive ;) A possible workaround for this would be to use minigzip instead of gunzip. You can see my solution as just another workaround. The archives for this port now just work[tm] - I know this isn't the perfect solution for any length of time. ;) I have proposed a potential long term solution by replacing GNU gzip with BSD gzip, as discussed in recent -current mailing list. I read that :) I will try out your patches. Regards, Philipp -- www.familie-ost.info/~pj ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: What is this?
On Fri, Oct 13, 2006 at 07:00:56PM +0200, Heino Tiedemann wrote: > Hi One thing i do not understand: > > ,[ ports/UPDATING ] > | 20061009: > | ^ (LOO AT THIS!) > | AFFECTS: users of any ports using Python > | AUTHOR: [EMAIL PROTECTED] > | > | After upgrading of lang/python, you must rebuild all its consumer > | ports to make them get ready to Python 2.5. > | ^^ > | To do this, you will need to: > | pkgdb -uf && cd /usr/ports/lang/python && make upgrade-site-packages > ` > > > vs: > > ,[ ports/lang/python/Makefile ] > | ports/lang/python/Makefile,v 1.157 2006/10/13 > |^^ > | PORTNAME= python > | PORTVERSION=2.4.3 > | ^ > ` > > > finally: > > 1) In ports/UPDATING is python 2.5 mentioned on 9th october. > 2) in the makefile of lang/python is the perversion 2.4.3 on 13th october > > So, what is now correct? > > How should i deal with the stale dependencies? > See this commit message and the thread after it: http://lists.freebsd.org/pipermail/cvs-ports/2006-October/107946.html -- Vasil Dimov [EMAIL PROTECTED] % The only difference between the saint and the sinner is that every saint has a past and every sinner has a future. -- Oscar Wilde pgptdgKFhIuZI.pgp Description: PGP signature
Re: What is this?
On Fri, 13 Oct 2006 12:00:56 -0500, Heino Tiedemann <[EMAIL PROTECTED]> wrote: Hi One thing i do not understand: ,[ ports/UPDATING ] | 20061009: | ^ (LOO AT THIS!) | AFFECTS: users of any ports using Python | AUTHOR: [EMAIL PROTECTED] | | After upgrading of lang/python, you must rebuild all its consumer | ports to make them get ready to Python 2.5. | ^^ | To do this, you will need to: | pkgdb -uf && cd /usr/ports/lang/python && make upgrade-site-packages ` vs: ,[ ports/lang/python/Makefile ] | ports/lang/python/Makefile,v 1.157 2006/10/13 |^^ | PORTNAME= python | PORTVERSION= 2.4.3 | ^ ` finally: 1) In ports/UPDATING is python 2.5 mentioned on 9th october. 2) in the makefile of lang/python is the perversion 2.4.3 on 13th october So, what is now correct? http://lists.freebsd.org/pipermail/cvs-ports/2006-October/107946.html Cheers, Mezz How should i deal with the stale dependencies? Heino -- [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]"
php5-5.1.6 & 5.1.6_1
Hi - I'm running 6.2 PRERELEASE #2 with my ports tree current to this morning (around 9am GMT-8). i386 with a Pentium 4 3.2Ghz It took some massaging, but I was finally able to get all the ports re-compiled except one, that in the subject line. php5-5.1.6 refuses to build because of Known Vulnerabilities: php -- _ecalloc integer overflow vulnerability, php5-5.1.6_1 refuses to build also because of Known Vulnerabilities: php -- open_basedir race condition vulnerabilities. Any suggestions? --Bill ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.1.6 & 5.1.6_1
On 10/13/06, Bill Blue <[EMAIL PROTECTED]> wrote: Hi - I'm running 6.2 PRERELEASE #2 with my ports tree current to this morning (around 9am GMT-8). i386 with a Pentium 4 3.2Ghz It took some massaging, but I was finally able to get all the ports re-compiled except one, that in the subject line. php5-5.1.6 refuses to build because of Known Vulnerabilities: php -- _ecalloc integer overflow vulnerability, php5-5.1.6_1 refuses to build also because of Known Vulnerabilities: php -- open_basedir race condition vulnerabilities. Any suggestions? You can install the port by defining DISABLE_VULNERABILITIES when building/installing the port. But you must understand that the installed port will have a security vulnerability. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: php5-5.1.6 & 5.1.6_1
On Oct 13, 2006, at 10:43 AM, Bill Blue wrote: It took some massaging, but I was finally able to get all the ports re-compiled except one, that in the subject line. php5-5.1.6 refuses to build because of Known Vulnerabilities: php -- _ecalloc integer overflow vulnerability, php5-5.1.6_1 refuses to build also because of Known Vulnerabilities: php -- open_basedir race condition vulnerabilities. Any suggestions? 1) Install PHP anyway, knowing that it contains known, exploitable vulnerabilities, via: cd /usr/ports/lang/php5 && DISABLE_VULNERABILITIES=yes make install Be aware that people are actively exploiting PHP-based apps using this hole right now. Be prepared to reinstall your machine completely from scratch after it gets hacked. 2) Live without PHP and anything which uses it. I recommend choosing option #2, where possible, otherwise restricting the use of PHP to machines which do not contain confidential or important data, and are kept in your network's DMZ or similiar "semi- trusted" subnet, rather than on your internal LAN. -- -Chuck ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: man hier? -- FreeBSD Port: sysutils/fusefs-kmod
Florent Thoumie wrote: > On Thu, 2006-10-12 at 18:33 +0200, martinko wrote: >> Hello, >> >> I wonder what is the reasoning behind fusefs-kmod port way of dealing >> with kernel module(s). >> I remember iwi ports putting their modules into /boot/modules and then >> one only had to edit /boot/loader.conf[.local] >> Now fusefs-kmod creates new directory /usr/local/modules where it puts >> its module, then it optionally edit /etc/sysctl.conf to modify >> kern.module_path and rc.conf to run /usr/local/etc/rc.d/fusefs script. >> Is all of this really necessary and why please ?? > > It makes the port/package PREFIX-clean. I could have done that for intel > firmware ports but I thought it would be too painful for the end-user. > I see. It's just that it feels too complicated and it doesn't look very nice to me, either. :-/ So is /usr/local/modules the final location of 3rd party modules? I mean was it agreed on or any port can choose it's own directory? Also, it seems to me like too much overhead to create rc.d script for each such a port only to allow it to load kernel module. I mean couldn't we have something like there's for local libraries or rc scripts? The paths are already preset. Well, I only would like to see it simplified and standardised somehow. But I'm pretty sure you guys will come up with a good solution. Thanks for your effort. Regards, Martin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: epsilon does not compile on freebsd-6 stable.
Ok, I did what you suggested and everything is alright now :) Thanx, Vassilis On Wed, Oct 11, 2006 at 11:44:14PM +0400, Stanislav Sedov wrote: > On Wed, 11 Oct 2006 15:48:09 +0300 > Laganakos Vassilis <[EMAIL PROTECTED]> mentioned: > > > Hi, > > > > I recently attempted to upgrade the enlightenment-devel to > > enlightenment-20060926 and there appears to be a problem in > > compiling the /graphics/epsilon port. > > > > I'm using freebsd-6-stable and I'm up to date. What could have caused > > this problem? > > > > Deinstall old epsilon before compilling the new one. It would be > preferrable to deinstall all old e17 libraries before upgrading as > there was a huge API breakage and X11BASE->LOCALBASE move. > > -- > Stanislav Sedov <[EMAIL PROTECTED]>[[??, ??]] > PGP id: 0xEB269581 http://people.freebsd.org/~stas/stas.key.asc > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.5 (FreeBSD) > > iD8DBQFFLUmUK/VZk+smlYERAhdMAJ9sU77T23Z5sGWTpQQwlr8Q0bBNyQCcDtoz > QVLbz19p4BU083VvpVZGnUc= > =JNrT > -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]"
pdflib fetch error
hey all,i can't fetch the distfile when i update pdflib,would anyone fix it? - root[/usr/ports/print/pdflib] 0 # make fetch ===> Vulnerability check disabled, database not found => PDFlib-Lite-7.0.0.tar.gz doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from http://www.pdflib.de/binaries/PDFlib/700/. fetch: http://www.pdflib.de/binaries/PDFlib/700/PDFlib-Lite-7.0.0.tar.gz: Not Found => Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/. fetch: ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/PDFlib-Lite-7.0.0.tar.gz: File unavailable (e.g., file not found, no ac cess) => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles/ and try again. *** Error code 1 -- thanks ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: pdflib fetch error
On 10/13/06, lveax <[EMAIL PROTECTED]> wrote: hey all,i can't fetch the distfile when i update pdflib,would anyone fix it? Looks like the file is no longer on the web site. Instead there is a new version: http://www.pdflib.com/binaries/PDFlib/700/PDFlib-Lite-7.0.0p1.tar.gz From the changes.txt = PDFlib 7.0.0p1 (October 11, 2006) = - 2006-10-10 Preparations and minor changes for iSeries builds. - 2006-10-10 (bug #900) Contrary to the documentation, the "SearchPath" resource category was not implemented with case-insensitive handling of the category name. - 2006-10-09 (bug #899) PDFlib Lite could crash or create invalid PDF output due to a problem in preparing the source code packages. - 2006-10-09 (bug #891) Fixed a problem with varargs handling which showed up in some 64-bit builds. Scot -- DISCLAIMER: No electrons were mamed while sending this message. Only slightly bruised. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
