Re: apr-gdbm-db42 upgrade conflicting with libtool
> Troy wrote: > > Updated all ports to python 26 and the problem still exists: > > > > pkg_info|grep py > > boost-python-libs-1.39.0 Framework for interfacing Python and C++ > > p5-Clone-0.31 Clone - recursively copy Perl datatypes > > py26-dbus-0.83.0_1 Python bindings for the D-BUS messaging system > > py26-elementtree-1.2.6_1 Container for hierarchical data structures > > written in Pytho > > py26-sip-4.8.2,1Python to C and C++ bindings generator > > py26-xml-0.8.4_2PyXML: Python XML library enhancements > > python26-2.6.2_1An interpreted object-oriented programming language > > ruby18-bdb-0.6.5_1 Ruby interface to Sleepycat's Berkeley DB revision > > 2 or lat > > xdpyinfo-1.0.3 Display information utility for X > > > > checking for stdint.h... yes > > checking for unistd.h... yes > > checking minix/config.h usability... no > > checking minix/config.h presence... no > > checking for minix/config.h... no > > checking whether it is safe to define __EXTENSIONS__... yes > > checking for library containing strerror... none required > > checking whether system uses EBCDIC... no > > performing libtool configuration... > > ./configure: 9753: Syntax error: word unexpected (expecting ")") > > *** Error code 2 > > > > Stop in /usr/ports/devel/apr. > > *** Error code 1 > > > > Stop in /usr/ports/devel/apr. > > *** Error code 1 > > > > Stop in /usr/ports/devel/apr. > > ** Command failed [exit code 1]: /usr/bin/script -qa > > /tmp/portinstall20090810-73192-8x2jso-0 env make reinstall > > ** Fix the installation problem and try again. > > ** Listing the failed packages (-:ignored / *:skipped / !:failed) > >! devel/apr (install error) > > > > > > FreeBSD somedomain 7.2-STABLE FreeBSD 7.2-STABLE #0: Sat May 23 > > 10:45:33 CDT 2009 some...@domain /usr/obj/usr/src/sys/kernel amd64 > > > > Any thoughts? > > > > -Troy > > > > ___ > > 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" > > Just to add to this the following warnings came up when trying to build > apr. I also deinstalled libtool and it installs just fine. I also > researched these errors and someone said it was related to gettext. I > reinstalled it just to be safe and still it did not change the outcome. > > > Copying libtool helper files ... > buildconf: Using libtool.m4 at /usr/local/share/aclocal/libtool.m4. > Creating include/arch/unix/apr_private.h.in ... > configure.in:190: warning: LTOPTIONS_VERSION is m4_require'd but not > m4_defun'd > build/libtool.m4:67: LT_INIT is expanded from... > build/libtool.m4:102: AC_PROG_LIBTOOL is expanded from... > configure.in:190: the top level > configure.in:190: warning: LTSUGAR_VERSION is m4_require'd but not > m4_defun'd > configure.in:190: warning: LTVERSION_VERSION is m4_require'd but not > m4_defun'd > configure.in:190: warning: LTOBSOLETE_VERSION is m4_require'd but not > m4_defun'd > Creating configure ... > configure.in:190: warning: LTOPTIONS_VERSION is m4_require'd but not > m4_defun'd > build/libtool.m4:67: LT_INIT is expanded from... > build/libtool.m4:102: AC_PROG_LIBTOOL is expanded from... > configure.in:190: the top level > configure.in:190: warning: LTSUGAR_VERSION is m4_require'd but not > m4_defun'd > configure.in:190: warning: LTVERSION_VERSION is m4_require'd but not > m4_defun'd > configure.in:190: warning: LTOBSOLETE_VERSION is m4_require'd but not > m4_defun'd > configure:9755: error: possibly undefined macro: m4_ifval > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. > configure:12392: error: possibly undefined macro: _LT_SET_OPTIONS > configure:12392: error: possibly undefined macro: LT_INIT did you apply the following in updating?? 20090608: AFFECTS: users of lang/python* and py-* AUTHOR: m...@freebsd.org The default version of Python has been changed from 2.5.x to 2.6.x. If you have 2.5.x installed, perform an upgrade of lang/python25 to lang/python26 with one of the following commands: If using portupgrade: # portupgrade -o lang/python26 lang/python25 If using portmaster: # portmaster -o lang/python26 lang/python25 If you want to retain 2.5.x as default Python version, set the PYTHON_DEFAULT_VERSION variable to 'python2.5' (without quotes) in /etc/make.conf, then go to lang/python and perform the following command: # portupgrade -R python Once the installed Python has been updated to 2.6, by using the method above, it is required to run the upgrade-site-packages target in lang/python to assure that site-packages are made available to the new Python version. If using portupgrade: # cd /usr/ports/lang/python && make upgrade-site-packages If using portmaster: # cd /usr/ports/lang/python && make upgrade-site-packages -DUSE_PORTMASTER The portmaster case can tak
MOVED and UPDATING delivered with packages
The portmgr team has enhanced the pointyhead scripts to publish MOVED and UPDATING files together with the INDEX files that kports and pkg_upgrade use for binary package updating. http://www.freebsd.org/cgi/query-pr.cgi?pr=135024 Many thanks to the portmgr team! I hope I will find the time to update pkg_upgrade before the 8.0 release. ___ 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: MOVED and UPDATING delivered with packages
On Tue, 11 Aug 2009 10:52:31 +0200, Dominic Fandrey wrote: > The portmgr team has enhanced the pointyhead scripts to publish MOVED > and UPDATING files together with the INDEX files that kports and > pkg_upgrade use for binary package updating. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=135024 > Very much appreciated but how about also providing them in bzip2 compressed form ? Especially INDEX, since it's is so large and compresses so good: # ls -l /usr/ports/INDEX-8* -rw-r--r-- 1 root wheel 19435698 Jul 25 06:20 /usr/ports/INDEX-8 -rw-r--r-- 1 root wheel 1295390 Jul 23 13:09 /usr/ports/INDEX-8.bz2 ___ 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: apr-gdbm-db42 upgrade conflicting with libtool
David Southwell wrote: Troy wrote: Updated all ports to python 26 and the problem still exists: pkg_info|grep py boost-python-libs-1.39.0 Framework for interfacing Python and C++ p5-Clone-0.31 Clone - recursively copy Perl datatypes py26-dbus-0.83.0_1 Python bindings for the D-BUS messaging system py26-elementtree-1.2.6_1 Container for hierarchical data structures written in Pytho py26-sip-4.8.2,1Python to C and C++ bindings generator py26-xml-0.8.4_2PyXML: Python XML library enhancements python26-2.6.2_1An interpreted object-oriented programming language ruby18-bdb-0.6.5_1 Ruby interface to Sleepycat's Berkeley DB revision 2 or lat xdpyinfo-1.0.3 Display information utility for X checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for library containing strerror... none required checking whether system uses EBCDIC... no performing libtool configuration... ./configure: 9753: Syntax error: word unexpected (expecting ")") *** Error code 2 Stop in /usr/ports/devel/apr. *** Error code 1 Stop in /usr/ports/devel/apr. *** Error code 1 Stop in /usr/ports/devel/apr. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall20090810-73192-8x2jso-0 env make reinstall ** Fix the installation problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! devel/apr (install error) FreeBSD somedomain 7.2-STABLE FreeBSD 7.2-STABLE #0: Sat May 23 10:45:33 CDT 2009 some...@domain /usr/obj/usr/src/sys/kernel amd64 Any thoughts? -Troy ___ 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" Just to add to this the following warnings came up when trying to build apr. I also deinstalled libtool and it installs just fine. I also researched these errors and someone said it was related to gettext. I reinstalled it just to be safe and still it did not change the outcome. Copying libtool helper files ... buildconf: Using libtool.m4 at /usr/local/share/aclocal/libtool.m4. Creating include/arch/unix/apr_private.h.in ... configure.in:190: warning: LTOPTIONS_VERSION is m4_require'd but not m4_defun'd build/libtool.m4:67: LT_INIT is expanded from... build/libtool.m4:102: AC_PROG_LIBTOOL is expanded from... configure.in:190: the top level configure.in:190: warning: LTSUGAR_VERSION is m4_require'd but not m4_defun'd configure.in:190: warning: LTVERSION_VERSION is m4_require'd but not m4_defun'd configure.in:190: warning: LTOBSOLETE_VERSION is m4_require'd but not m4_defun'd Creating configure ... configure.in:190: warning: LTOPTIONS_VERSION is m4_require'd but not m4_defun'd build/libtool.m4:67: LT_INIT is expanded from... build/libtool.m4:102: AC_PROG_LIBTOOL is expanded from... configure.in:190: the top level configure.in:190: warning: LTSUGAR_VERSION is m4_require'd but not m4_defun'd configure.in:190: warning: LTVERSION_VERSION is m4_require'd but not m4_defun'd configure.in:190: warning: LTOBSOLETE_VERSION is m4_require'd but not m4_defun'd configure:9755: error: possibly undefined macro: m4_ifval If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure:12392: error: possibly undefined macro: _LT_SET_OPTIONS configure:12392: error: possibly undefined macro: LT_INIT did you apply the following in updating?? 20090608: AFFECTS: users of lang/python* and py-* AUTHOR: m...@freebsd.org The default version of Python has been changed from 2.5.x to 2.6.x. If you have 2.5.x installed, perform an upgrade of lang/python25 to lang/python26 with one of the following commands: If using portupgrade: # portupgrade -o lang/python26 lang/python25 If using portmaster: # portmaster -o lang/python26 lang/python25 If you want to retain 2.5.x as default Python version, set the PYTHON_DEFAULT_VERSION variable to 'python2.5' (without quotes) in /etc/make.conf, then go to lang/python and perform the following command: # portupgrade -R python Once the installed Python has been updated to 2.6, by using the method above, it is required to run the upgrade-site-packages target in lang/python to assure that site-packages are made available to the new Python version. If using portupgrade: # cd /usr/ports/lang/python && make upgrade-site-packages If using portmaster: # cd /usr/ports/lang/python && make upgrade-site-packages -DUSE_PORTMASTER The portmaster case can take quite some time to complete due to the lack of cached information that the portupgrade suite uses (specifically pkg_which). This is not the fault of portmaster. I removed the old versions and installed the new versions f
Re: apr-gdbm-db42 upgrade conflicting with libtool
Troy wrote: David Southwell wrote: Troy wrote: Updated all ports to python 26 and the problem still exists: pkg_info|grep py boost-python-libs-1.39.0 Framework for interfacing Python and C++ p5-Clone-0.31 Clone - recursively copy Perl datatypes py26-dbus-0.83.0_1 Python bindings for the D-BUS messaging system py26-elementtree-1.2.6_1 Container for hierarchical data structures written in Pytho py26-sip-4.8.2,1Python to C and C++ bindings generator py26-xml-0.8.4_2PyXML: Python XML library enhancements python26-2.6.2_1An interpreted object-oriented programming language ruby18-bdb-0.6.5_1 Ruby interface to Sleepycat's Berkeley DB revision 2 or lat xdpyinfo-1.0.3 Display information utility for X checking for stdint.h... yes checking for unistd.h... yes checking minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for library containing strerror... none required checking whether system uses EBCDIC... no performing libtool configuration... ./configure: 9753: Syntax error: word unexpected (expecting ")") *** Error code 2 Stop in /usr/ports/devel/apr. *** Error code 1 Stop in /usr/ports/devel/apr. *** Error code 1 Stop in /usr/ports/devel/apr. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portinstall20090810-73192-8x2jso-0 env make reinstall ** Fix the installation problem and try again. ** Listing the failed packages (-:ignored / *:skipped / !:failed) ! devel/apr (install error) FreeBSD somedomain 7.2-STABLE FreeBSD 7.2-STABLE #0: Sat May 23 10:45:33 CDT 2009 some...@domain /usr/obj/usr/src/sys/kernel amd64 Any thoughts? -Troy ___ 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" Just to add to this the following warnings came up when trying to build apr. I also deinstalled libtool and it installs just fine. I also researched these errors and someone said it was related to gettext. I reinstalled it just to be safe and still it did not change the outcome. Copying libtool helper files ... buildconf: Using libtool.m4 at /usr/local/share/aclocal/libtool.m4. Creating include/arch/unix/apr_private.h.in ... configure.in:190: warning: LTOPTIONS_VERSION is m4_require'd but not m4_defun'd build/libtool.m4:67: LT_INIT is expanded from... build/libtool.m4:102: AC_PROG_LIBTOOL is expanded from... configure.in:190: the top level configure.in:190: warning: LTSUGAR_VERSION is m4_require'd but not m4_defun'd configure.in:190: warning: LTVERSION_VERSION is m4_require'd but not m4_defun'd configure.in:190: warning: LTOBSOLETE_VERSION is m4_require'd but not m4_defun'd Creating configure ... configure.in:190: warning: LTOPTIONS_VERSION is m4_require'd but not m4_defun'd build/libtool.m4:67: LT_INIT is expanded from... build/libtool.m4:102: AC_PROG_LIBTOOL is expanded from... configure.in:190: the top level configure.in:190: warning: LTSUGAR_VERSION is m4_require'd but not m4_defun'd configure.in:190: warning: LTVERSION_VERSION is m4_require'd but not m4_defun'd configure.in:190: warning: LTOBSOLETE_VERSION is m4_require'd but not m4_defun'd configure:9755: error: possibly undefined macro: m4_ifval If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure:12392: error: possibly undefined macro: _LT_SET_OPTIONS configure:12392: error: possibly undefined macro: LT_INIT did you apply the following in updating?? 20090608: AFFECTS: users of lang/python* and py-* AUTHOR: m...@freebsd.org The default version of Python has been changed from 2.5.x to 2.6.x. If you have 2.5.x installed, perform an upgrade of lang/python25 to lang/python26 with one of the following commands: If using portupgrade: # portupgrade -o lang/python26 lang/python25 If using portmaster: # portmaster -o lang/python26 lang/python25 If you want to retain 2.5.x as default Python version, set the PYTHON_DEFAULT_VERSION variable to 'python2.5' (without quotes) in /etc/make.conf, then go to lang/python and perform the following command: # portupgrade -R python Once the installed Python has been updated to 2.6, by using the method above, it is required to run the upgrade-site-packages target in lang/python to assure that site-packages are made available to the new Python version. If using portupgrade: # cd /usr/ports/lang/python && make upgrade-site-packages If using portmaster: # cd /usr/ports/lang/python && make upgrade-site-packages -DUSE_PORTMASTER The portmaster case can take quite some time to complete due to the lack of cached information that the portupgrade suite uses (specifically pkg_which). This is not the fault of portmaster. I removed the old versions and in
Re: MOVED and UPDATING delivered with packages
Marcin Wisnicki wrote: > On Tue, 11 Aug 2009 10:52:31 +0200, Dominic Fandrey wrote: > >> The portmgr team has enhanced the pointyhead scripts to publish MOVED >> and UPDATING files together with the INDEX files that kports and >> pkg_upgrade use for binary package updating. >> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=135024 >> > > Very much appreciated but how about also providing them in bzip2 > compressed form ? > Especially INDEX, since it's is so large and compresses > so good: There is a different PR for this (by the author of kports): http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/131440 ___ 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: graphics/gocr
On Tue, 11 Aug 2009 06:40:16 +0100 Matthew Seaman wrote: > Sourceforge seems to have gone re-direct happy. Downloading anything > from there seems to require following at least two 302 redirects -- > eg: > Notice how it's forced me to go to the Kent mirror? (Not that I'm > complaining -- UKC is only about 15 miles up the road in Canterbury) Why not put some nearby mirrors in MASTER_SORT_REGEX? ___ 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: MOVED and UPDATING delivered with packages
On Tue, Aug 11, 2009 at 03:00:56PM +0200, Dominic Fandrey wrote: > Marcin Wisnicki wrote: > > On Tue, 11 Aug 2009 10:52:31 +0200, Dominic Fandrey wrote: > > > >> The portmgr team has enhanced the pointyhead scripts to publish MOVED > >> and UPDATING files together with the INDEX files that kports and > >> pkg_upgrade use for binary package updating. > >> > >> http://www.freebsd.org/cgi/query-pr.cgi?pr=135024 > >> > > > > Very much appreciated but how about also providing them in bzip2 > > compressed form ? > > Especially INDEX, since it's is so large and compresses > > so good: > > There is a different PR for this (by the author of kports): > > http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/131440 Oh, somehow I missed this one. Looking into it now. Best, -erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org pgpFRqHAFuT52.pgp Description: PGP signature
SourceForge changing file distribution scheme!
Hi!
I've noticed that SF is changing file distribution scheme significantly,
and I guess that will affect many ports and maybe infrastructure.
Hopefully, the change only seem to affect new distfiles, so for now we
should just do extra checks for updates of ports hosted on sourceforge.
Here's what happens. This is math/maxima port. Old version:
---
% wget http://kent.dl.sourceforge.net/sourceforge/maxima/maxima-5.18.0.tar.gz
-O/dev/null
--2009-08-11 19:11:07--
http://kent.dl.sourceforge.net/sourceforge/maxima/maxima-5.18.0.tar.gz
Resolving kent.dl.sourceforge.net... 212.219.56.167
Connecting to kent.dl.sourceforge.net|212.219.56.167|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 20437623 (19M) [application/x-gzip]
Saving to: `/dev/null'
2% [>
---
New version:
---
% wget http://kent.dl.sourceforge.net/sourceforge/maxima/maxima-5.19.0.tar.gz
-O/dev/null
--2009-08-11 19:13:20--
http://kent.dl.sourceforge.net/sourceforge/maxima/maxima-5.19.0.tar.gz
Resolving kent.dl.sourceforge.net... 212.219.56.167
Connecting to kent.dl.sourceforge.net|212.219.56.167|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location:
http://downloads.sourceforge.net/sourceforge/maxima/maxima-5.19.0.tar.gz?download&failedmirror=kent.dl.sourceforge.net
[following]
--2009-08-11 19:13:20--
http://downloads.sourceforge.net/sourceforge/maxima/maxima-5.19.0.tar.gz?download&failedmirror=kent.dl.sourceforge.net
Resolving downloads.sourceforge.net... 216.34.181.59
Connecting to downloads.sourceforge.net|216.34.181.59|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location:
http://sunet.dl.sourceforge.net/project/maxima/Maxima-source/5.19.0-source/maxima-5.19.0.tar.gz
[following]
--2009-08-11 19:13:21--
http://sunet.dl.sourceforge.net/project/maxima/Maxima-source/5.19.0-source/maxima-5.19.0.tar.gz
Resolving sunet.dl.sourceforge.net... 194.71.11.73
Connecting to sunet.dl.sourceforge.net|194.71.11.73|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 20566185 (20M) [application/x-gzip]
Saving to: `/dev/null'
2% [>
---
As you can see, the distfile now redirects to another path and also
another mirror. As fetch doesn't follow redirects by default, this won't
work. My idea is that in addition to [old scheme]
MASTER_SITE_SOURCEFORGE+= \
http://${mirror}.dl.sourceforge.net/sourceforge/%SUBDIR%/
we'll need to add
MASTER_SITE_SOURCEFORGE_NEW+= \
http://${mirror}.dl.sourceforge.net/project/%SUBDIR%/
with coresponding macro (SF -> SFNEW)
and we'll have to add pretty complex MASTER_SITE_SUBDIR to each updated
port from SF.
Any comments?
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.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: SourceForge changing file distribution scheme!
On Tue, Aug 11, 2009 at 07:20:54PM +0400, Dmitry Marakasov wrote:
> Hi!
hi Dmitry,
>
> I've noticed that SF is changing file distribution scheme significantly,
> and I guess that will affect many ports and maybe infrastructure.
I fear the same, unfortunately. However, I haven't as yet been able to
identify a consistency in the new scheme. Is it only new files that are
put in the /project/ folder? Will all files slowly migrate to the new
file structure? Or is there something different internally in SF
whether something is a project or just a file?
>
> As you can see, the distfile now redirects to another path and also
> another mirror. As fetch doesn't follow redirects by default, this won't
> work. My idea is that in addition to [old scheme]
>
> MASTER_SITE_SOURCEFORGE+= \
> http://${mirror}.dl.sourceforge.net/sourceforge/%SUBDIR%/
>
> we'll need to add
>
> MASTER_SITE_SOURCEFORGE_NEW+= \
> http://${mirror}.dl.sourceforge.net/project/%SUBDIR%/
>
> with coresponding macro (SF -> SFNEW)
>
> and we'll have to add pretty complex MASTER_SITE_SUBDIR to each updated
> port from SF.
>
I have received a similar patch from Sylvio Cesar, but this only fixes
the issue with the directory changing from sourceforge to project, it
doesn't address the changing of servers you also showed in the example.
This bit is more tricky, and I haven't found a way to predict the final
server/link yet unfortunately. I hope someone out there is better at
guessing this than me and can come up with a patch for both issues.
Cheers,
-erwin
--
Erwin Lansing http://droso.org
Prediction is very difficult
especially about the futureer...@freebsd.org
pgpVJSb7z3noN.pgp
Description: PGP signature
Re: SourceForge changing file distribution scheme!
On Tue, Aug 11, 2009 at 11:36 AM, Erwin Lansing wrote: > On Tue, Aug 11, 2009 at 07:20:54PM +0400, Dmitry Marakasov wrote: >> Hi! > > hi Dmitry, >> >> I've noticed that SF is changing file distribution scheme significantly, >> and I guess that will affect many ports and maybe infrastructure. > > I fear the same, unfortunately. However, I haven't as yet been able to > identify a consistency in the new scheme. Is it only new files that are > put in the /project/ folder? It doesn't appear so. See the PR I filed recently to fix a 'fetch failed' port [1]. I believe it is safe to assume this port was 'fetch'able until recently. [1] - http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/137597 -- Glen Barber ___ 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: SourceForge changing file distribution scheme!
* Dmitry Marakasov (amd...@amdmi3.ru) wrote:
Here's the patch I propose.
Unfortunately, there's no way to guess MASTER_SITE_SUBDIR (examples:
http://sunet.dl.sourceforge.net/project/maxima/Maxima-source/5.19.0-source/maxima-5.19.0.tar.gz
http://sunet.dl.sourceforge.net/project/lam/LAM/2.7.0/ldap-account-manager-2.7.0.tar.gz
) so for SFNEW it should be always set in the port.
I'm also thinking of writing to SF (their change also breaks at
least portscout). We may also consider switching to following
redirects in fetch.
--- bsd.sites.mk.patch begins here ---
Index: bsd.sites.mk
===
RCS file: /home/amdmi3/projects/freebsd/FreeBSD.cvs/ports/Mk/bsd.sites.mk,v
retrieving revision 1.478
diff -u -r1.478 bsd.sites.mk
--- bsd.sites.mk11 Aug 2009 06:58:24 - 1.478
+++ bsd.sites.mk11 Aug 2009 15:36:25 -
@@ -1172,12 +1172,20 @@
.endif
.if !defined(IGNORE_MASTER_SITE_SOURCEFORGE)
-.for mirror in superb-east nchc kent easynews ufpr mesh heanet # garr
+.for mirror in garr superb-east nchc kent easynews ufpr mesh heanet
MASTER_SITE_SOURCEFORGE+= \
http://${mirror}.dl.sourceforge.net/sourceforge/%SUBDIR%/
.endfor
.endif
+# new SourceForge url scheme
+.if !defined(IGNORE_MASTER_SITE_SOURCEFORGE_NEW)
+.for mirror in garr superb-east nchc kent easynews ufpr mesh heanet
+MASTER_SITE_SOURCEFORGE_NEW+= \
+ http://${mirror}.dl.sourceforge.net/project/%SUBDIR%/
+.endfor
+.endif
+
# official sf.net mirrors that don't mirror all projects, check
# http://prdownloads.sourceforge.net/%SUBDIR%/
.if !defined(IGNORE_MASTER_SITE_SOURCEFORGE_EXTENDED)
@@ -1494,7 +1502,7 @@
# Macro magic
MASTER_SITES_ABBREVS= CPAN:PERL_CPAN SF:SOURCEFORGE SFE:SOURCEFORGE_EXTENDED \
- SFJP:SOURCEFORGE_JP RF:RUBYFORGE
+ SFNEW:SOURCEFORGE_NEW SFJP:SOURCEFORGE_JP RF:RUBYFORGE
MASTER_SITES_SUBDIRS= \
APACHE_JAKARTA:${PORTNAME:S,-,/,}/source \
BERLIOS:${PORTNAME:L} \
--- bsd.sites.mk.patch ends here ---
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.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: SourceForge changing file distribution scheme!
On Tue, Aug 11, 2009 at 12:20 PM, Dmitry Marakasov wrote:
> Hi!
>
> I've noticed that SF is changing file distribution scheme significantly,
[...]
> As you can see, the distfile now redirects to another path and also
> another mirror. As fetch doesn't follow redirects by default, this won't
> work. My idea is that in addition to [old scheme]
>
> MASTER_SITE_SOURCEFORGE+= \
>http://${mirror}.dl.sourceforge.net/sourceforge/%SUBDIR%/
>
> we'll need to add
>
> MASTER_SITE_SOURCEFORGE_NEW+= \
>http://${mirror}.dl.sourceforge.net/project/%SUBDIR%/
>
> with coresponding macro (SF -> SFNEW)
>
> and we'll have to add pretty complex MASTER_SITE_SUBDIR to each updated
> port from SF.
>
> Any comments?
I found the same problem when attempted to fetch the new files for
Ayttm. Also noticed that the files are missing on some mirrors. As a
workaround, I replaced "SF" in MASTER_SITES by
PORTNAME= ayttm
PORTVERSION=0.5.0.111
CATEGORIES= net-im
.for mirror in nchc kent ufpr heanet switch puzzle osdn ovh
MASTER_SITES+=http://${mirror}.dl.sourceforge.net/project/ayttm/ayttm/${PORTVERSION:R}-${PORTVERSION:E}/
.endfor
DISTNAME= ${PORTNAME}-${PORTVERSION:R}-${PORTVERSION:E}
--
My preferred quotation of Robert Louis Stevenson is "You cannot
make an omelette without breaking eggs". Not because I like the
omelettes, but because I like the sound of eggs being broken.
___
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: SourceForge changing file distribution scheme!
On Tue, Aug 11, 2009 at 07:41:03PM +0400, Dmitry Marakasov wrote: > * Dmitry Marakasov (amd...@amdmi3.ru) wrote: > > Here's the patch I propose. > > Unfortunately, there's no way to guess MASTER_SITE_SUBDIR (examples: > > http://sunet.dl.sourceforge.net/project/maxima/Maxima-source/5.19.0-source/maxima-5.19.0.tar.gz > http://sunet.dl.sourceforge.net/project/lam/LAM/2.7.0/ldap-account-manager-2.7.0.tar.gz Right, that's the third issue making it completely impossible to predict the final URL: - sourceforge vs project - subfolder syntax - bouncing between CDR servers > > ) so for SFNEW it should be always set in the port. > > I'm also thinking of writing to SF (their change also breaks at Writing SF might actually our best option here. -erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org pgp0UNkCZxGEq.pgp Description: PGP signature
Re: SourceForge changing file distribution scheme!
* Erwin Lansing (er...@freebsd.org) wrote:
> > I've noticed that SF is changing file distribution scheme significantly,
> > and I guess that will affect many ports and maybe infrastructure.
>
> I fear the same, unfortunately. However, I haven't as yet been able to
> identify a consistency in the new scheme.
It seems that there's no consistency. There are 3 components of URL
between /project/ and filename, and they are seemingly arbitary.
> Is it only new files that are put in the /project/ folder? Will
> all files slowly migrate to the new file structure? Or is there
> something different internally in SF whether something is a project
> or just a file?
I guess it's done automatically for all new releases. However, I can
check.
> > As you can see, the distfile now redirects to another path and also
> > another mirror. As fetch doesn't follow redirects by default, this won't
> > work. My idea is that in addition to [old scheme]
> >
> > MASTER_SITE_SOURCEFORGE+= \
> > http://${mirror}.dl.sourceforge.net/sourceforge/%SUBDIR%/
> >
> > we'll need to add
> >
> > MASTER_SITE_SOURCEFORGE_NEW+= \
> > http://${mirror}.dl.sourceforge.net/project/%SUBDIR%/
> >
> > with coresponding macro (SF -> SFNEW)
> >
> > and we'll have to add pretty complex MASTER_SITE_SUBDIR to each updated
> > port from SF.
> >
> I have received a similar patch from Sylvio Cesar, but this only fixes
> the issue with the directory changing from sourceforge to project, it
> doesn't address the changing of servers you also showed in the example.
There's no problem with changing servers. It just redirects to another
mirror, if you use old scheme for new files, but if you use new scheme
URL, there're no redirects and it should just work with our mirror set
as before.
--
Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D
amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.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: SourceForge changing file distribution scheme!
* Erwin Lansing (er...@freebsd.org) wrote: > Writing SF might actually our best option here. I've written them through feedback form. Not sure it'll reach them, so I'll also submit a proper support request when I get home (~in 6hrs). I don't have my SF password with me currently :( -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.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: SourceForge changing file distribution scheme!
* Erwin Lansing [2009-08-11]: > On Tue, Aug 11, 2009 at 07:41:03PM +0400, Dmitry Marakasov wrote: > > * Dmitry Marakasov (amd...@amdmi3.ru) wrote: > > > > Here's the patch I propose. > > > > Unfortunately, there's no way to guess MASTER_SITE_SUBDIR (examples: > > > > http://sunet.dl.sourceforge.net/project/maxima/Maxima-source/5.19.0-source/maxima-5.19.0.tar.gz > > http://sunet.dl.sourceforge.net/project/lam/LAM/2.7.0/ldap-account-manager-2.7.0.tar.gz > > Right, that's the third issue making it completely impossible to predict > the final URL: > - sourceforge vs project > - subfolder syntax > - bouncing between CDR servers > > > > ) so for SFNEW it should be always set in the port. > > > > I'm also thinking of writing to SF (their change also breaks at > > Writing SF might actually our best option here. I guess many of you have projects on SF and know this already, but the changes is part of the new easy-to-use File Release System. Read more http://sourceforge.net/apps/trac/sourceforge/wiki/Release%20files%20for%20download Regarding the structure of existing packages/releases - quoting http://sourceforge.net/apps/wordpress/sourceforge/2009/07/22/file-release-system-frs-update-complete-2009-07-22/ We have also converted existing FRS data into a simple hierarchy based on existing package and release names. If you contact Daniel Hinojosa (Sr. Manager, SourceForge.net) he will probably tell you how the conversion is done for existing packages. For new packages/releases there is no pattern - it's up to every package maintainer to decide the directory structure. In other words, the project/whatever/whatever/ must be set in each port - not just the filename. Hans ___ 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: [HEADSUP]: Ports freeze schedule for 8.0-RELEASE
Erwin Lansing wrote: > Below is the tentative schedule for the ports freeze in preparation for > 8.0-RELEASE. If any major delays occur in the overall release schedule, > the dates may be postponed, but please start preparing to have your > changed committed to the tree before August 17 to ensure they are > included in the release. Also, portmgr kindly asks anyone who has > anything major lined up to already from today start mailing portmgr > about these so we know what to expect and not be surprised by any major > fallout that might extend the short freeze we have planned. > > August 17: ports tree is frozen and package build begin > August 24: ports tree is thawed and final package builds begin > August 31: FreeBSD 8.0-RELEASE is released and ports tree is unfrozen Since the release date is slipping is this schedule going to be adjusted? Doug -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: [HEADSUP]: Ports freeze schedule for 8.0-RELEASE
On Tue, Aug 11, 2009 at 10:04:44AM -0700, Doug Barton wrote: > Erwin Lansing wrote: > > Below is the tentative schedule for the ports freeze in preparation for > > 8.0-RELEASE. If any major delays occur in the overall release schedule, > > the dates may be postponed, but please start preparing to have your > > changed committed to the tree before August 17 to ensure they are > > included in the release. Also, portmgr kindly asks anyone who has > > anything major lined up to already from today start mailing portmgr > > about these so we know what to expect and not be surprised by any major > > fallout that might extend the short freeze we have planned. > > > > August 17: ports tree is frozen and package build begin > > August 24: ports tree is thawed and final package builds begin > > August 31: FreeBSD 8.0-RELEASE is released and ports tree is unfrozen > > Since the release date is slipping is this schedule going to be adjusted? > Yes, we're waiting for word from re@ on by how much exactly, but expect the ports freeze to start at least a week later than the above days. I'll send a new HEADSUP as soon as the exact date is known. Best, -erwin -- Erwin Lansing http://droso.org Prediction is very difficult especially about the futureer...@freebsd.org pgpeVPDU36Zzn.pgp Description: PGP signature
distfiles and groups.google.com
Hello. Sorry for my English. I would like to write port for ReposStyle. This is open source stylesheet for the Subversion index web page. Please give me advise how I can get distfiles of this project. These files are available by this link http://groups.google.com/group/reposstyle/files, but the final zip file is available by dynamic link (ex. http://reposstyle.googlegroups.com/web/repos-style-2.0.zip?gda=mldqwUUw12lk1UvsIEMwf4K8gD3ZdgKDRLXt14ReAUFWPfo4j6AzGaACLVBgXTkjy_isydm-ncxEZ4rCAxOtc9DB4LrTGu1iLHeqhw4ZZRj3RjJ_-A) And I can't use only http://reposstyle.googlegroups.com/web/repos-style-2.0.zip Thanks. ___ 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"
graphics/netpbm & netpbm-devel
graphics/netpbm & netpbm-devel: These two ports dont list and CONFLICTS for either one of them. They do on the other hand list a conflict with "mgetty ???". Why don't these list conflicts with each other?. As of now I am doing cleanup once again for two versions of netpbm that have somehow been installed by portmaster during the mass confusion of graphics/jpeg. Best regards. -- Jason J. Hellenthal +1.616.403.8065 jas...@dataix.net ___ 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: graphics/netpbm & netpbm-devel
cc'ing the maintainer since this is an issue that needs to be addressed. Doug Jason J. Hellenthal wrote: > graphics/netpbm & netpbm-devel: > > These two ports dont list and CONFLICTS for either one of them. They do on > the other hand list a conflict with "mgetty ???". Why don't these list > conflicts with each other?. As of now I am doing cleanup once again for two > versions of netpbm that have somehow been installed by portmaster during the > mass confusion of graphics/jpeg. > > Best regards. > -- This .signature sanitized for your protection ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
firefox3 / libxul
I just installed my new laptop with -current doing a complete build, in the end, firefox3 does not start: /usr/local/lib/firefox3/firefox-bin /libexec/ld-elf.so.1: Shared object "libxul.so" not found, required by "firefox-bin" it is not entirely clear to me how it managed to compile against this lib, but not install it, but it may be a matter of PORTS dependencies being wrong, therefore this email. It might be reproducible, by taking a blank system and cd /usr/ports/www/firefox3 make all install clean which is essentially what my "sysbuild.sh" tool (see src/tools/tools) does. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ 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 Port: emacs-23.0.95_1
Hello, I've made some minor modifications to the emacs-devel port to update it to emacs version 23.1. Should I submit a PR or maybe you are waiting for some reason? Cheers, Joey Mingrone ___ 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: firefox3 / libxul
In message <21544.1250015...@critter.freebsd.dk>, Poul-Henning Kamp writes: > >I just installed my new laptop with -current doing a complete build, >in the end, firefox3 does not start: > >/usr/local/lib/firefox3/firefox-bin >/libexec/ld-elf.so.1: Shared object "libxul.so" not found, required by >"firefox-bin" Disregard this, I have found the problem, firefox does not tell you if it cannot create $HOME/.mozilla and just silently explodes. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 p...@freebsd.org | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. ___ 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: apr-gdbm-db42 upgrade conflicting with libtool
Can you please email me lines 9750-9759 from your file: /usr/local/share/libtool/libltdl/configure I want to see what error is being reported. The reported error does not seem to reflect the content of my libtdl/configure at that line number > ./configure: 9753: Syntax error: word unexpected (expecting ")") David ___ 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: distfiles and groups.google.com
* Alexander Kriventsov (a...@vl.ru) wrote: > I would like to write port for ReposStyle. This is open source > stylesheet for the Subversion index web page. > Please give me advise how I can get distfiles of this project. > These files are available by this link > http://groups.google.com/group/reposstyle/files, but the final zip file > is available by dynamic link (ex. > http://reposstyle.googlegroups.com/web/repos-style-2.0.zip?gda=mldqwUUw12lk1UvsIEMwf4K8gD3ZdgKDRLXt14ReAUFWPfo4j6AzGaACLVBgXTkjy_isydm-ncxEZ4rCAxOtc9DB4LrTGu1iLHeqhw4ZZRj3RjJ_-A) > And I can't use only > http://reposstyle.googlegroups.com/web/repos-style-2.0.zip Seems like the only way is to mirror the distfile on another host. I can mirror it for you: http://mirror.amdmi3.ru/distfiles/. -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.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: FreeBSD Port: openbgpd-4.5.20090709
Hello Mr. Sato,
Any update about these ?
Didn't you find my symptom on your box ?
Rgds,
--
Lasta Yani
- "Lasta Yani" wrote:
> Hello,
>
> Any update about this ?
>
>
> - "Lasta Yani" wrote:
>
> > - "Hiroki Sato" wrote:
> > >
> > > I think there is no problem with the configuration itself. Just
> in
> > > case, please send me the output of "bgpd -nv"? I will try to
> > > reproduce your symptom on my box.
> > >
> >
> > Hi,
> >
> > This is my configuration, output of bgpd -nv,
> >
> > nap1 = "119.110.122.5"
> > nap2 = "119.110.127.5"
> > keNAP = "{ 203.84.152.0/22 203.84.156.0/22 }"
> >
> > AS 24523
> > router-id 203.84.155.84
> > holdtime min 3
> > fib-update yes
> >
> > rde rib Adj-RIB-In no evaluate
> > rde rib Loc-RIB
> >
> > network 203.84.152.0/21
> > network 203.84.152.0/22
> > network 203.84.152.0/23
> > network 203.84.152.0/24
> > network 203.84.153.0/24
> > network 203.84.154.0/23
> > network 203.84.155.0/24
> > network 203.84.156.0/22
> > network 203.84.156.0/23
> > network 203.84.156.0/24
> > network 203.84.157.0/24
> > network 203.84.158.0/23
> > network 203.84.158.0/24
> > network 203.84.159.0/24
> >
> >
> > neighbor 119.110.127.5 {
> > descr "ke-NAP2"
> > remote-as 45147
> > announce all
> > enforce neighbor-as yes
> > announce IPv4 unicast
> > announce IPv6 none
> > softreconfig in yes
> > softreconfig out yes
> > }
> > neighbor 119.110.122.5 {
> > descr "ke-NAP1"
> > remote-as 45147
> > announce all
> > enforce neighbor-as yes
> > announce IPv4 unicast
> > announce IPv6 none
> > softreconfig in yes
> > softreconfig out yes
> > }
> >
> > match to 119.110.122.5 set { prepend-self 2 }
> > match to 119.110.127.5 set { prepend-self 2 }
> > deny from any
> > allow from 119.110.122.5 inet prefixlen 8 - 24
> > deny to any
> > allow to 119.110.127.5 prefix 203.84.156.0/22
> > allow to 119.110.127.5 prefix 203.84.152.0/22
> > allow to 119.110.122.5 prefix 203.84.156.0/22
> > allow to 119.110.122.5 prefix 203.84.152.0/22
> > deny from any prefix 0.0.0.0/0
> > deny from any prefix 10.0.0.0/8 prefixlen >= 8
> > deny from any prefix 172.16.0.0/12 prefixlen >= 12
> > deny from any prefix 192.0.2.0/24 prefixlen >= 24
> > deny from any prefix 169.254.0.0/16 prefixlen >= 16
> > deny from any prefix 192.168.0.0/16 prefixlen >= 16
> > deny from any prefix 240.0.0.0/4 prefixlen >= 4
> > deny from any prefix 224.0.0.0/4 prefixlen >= 4
> >
>
> Thank you,
> --
> Lasta Yani
___
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"
Stop in /usr/ports/graphics/aalib
bastion# uname -a
FreeBSD bastion.mordvap.net 7.2-RELEASE-p3 FreeBSD 7.2-RELEASE-p3 #1: Tue
Aug 11 19:19:21 CEST 2009
u...@bastion.host.net:/usr/obj/usr/src/sys/BASTION i386
checking whether ln -s works... (cached) yes
ltconfig: `/usr/local/share/libtool/config/ltmain.sh' does not exist
Try `ltconfig --help' for more information.
configure: error: libtool configure failed
===> Script "configure" failed unexpectedly.
Please report the problem to po...@freebsd.org [maintainer] and attach the
"/usr/ports/graphics/aalib/work/aalib-1.4.0/config.log" including the output
of the failure of your make command. Also, it might be a good idea to
provide
an overview of all packages installed on your system (e.g. an `ls
/var/db/pkg`).
*** Error code 1
Stop in /usr/ports/graphics/aalib.
*** Error code 1
Stop in /usr/ports/devel/sdl12.
*** Error code 1
Stop in /usr/ports/devel/sdl12.
*** Error code 1
Stop in /usr/ports/emulators/virtualbox.
*** Error code 1
#3
bastion# cat /usr/ports/graphics/aalib/work/aalib-1.4.0/config.log
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
configure:584: checking for a BSD compatible install
configure:637: checking whether build environment is sane
configure:694: checking whether make sets ${MAKE}
configure:740: checking for working aclocal
configure:753: checking for working autoconf
configure:766: checking for working automake
configure:779: checking for working autoheader
configure:792: checking for working makeinfo
configure:812: checking host system type
configure:833: checking target system type
configure:882: checking for gcc
configure:995: checking whether the C compiler (cc -O2 -fno-strict-aliasing
-pipe ) works
configure:1011: cc -o conftest -O2 -fno-strict-aliasing -pipe conftest.c
1>&5
configure:1037: checking whether the C compiler (cc -O2 -fno-strict-aliasing
-pipe ) is a cross-compiler
configure:1042: checking whether we are using GNU C
configure:1070: checking whether cc accepts -g
configure:1171: checking build system type
configure:1191: checking for ranlib
configure:1230: checking for ld used by GCC
configure:1292: checking if the linker (/usr/bin/ld) is GNU ld
configure:1308: checking for BSD-compatible nm
configure:1344: checking whether ln -s works
#
bastion# ls /var/db/pkg
alpine-2.00_1 jpeg-6b_7 libxcb-1.4
pico-alpine-2.00_1
aspell-0.60.6_2 kBuild-0.1.5.p1_1
libxml2-2.7.3 pkg-config-0.23_1
autoconf-2.13.000227_6 kbproto-1.0.3
libxslt-1.1.24_2pkgdb.db
autoconf-2.62 libICE-1.0.4_1,1
linux_base-fc-4_14 png-1.2.35
autoconf-wrapper-20071109 libSM-1.1.0_1,1 lua-5.1.4
popt-1.7_5
automake-1.10.1 libX11-1.2.1_1,1
lynx-2.8.7d13 portupgrade-2.4.6,2
automake-1.4.6_5libXau-1.0.4lzo2-2.03_2
python26-2.6.2_1
automake-1.9.6_3libXcursor-1.1.9_1 m4-1.4.12,1
randrproto-1.3.0
automake-wrapper-20071109 libXdmcp-1.0.2_1
mime-support-3.44.1 renderproto-0.9.3
bash-4.0.10_2 libXext-1.0.5,1
mrtg-2.16.2,1 rpm-3.0.6_14
bigreqsproto-1.0.2 libXfixes-4.0.3_1 nano-2.0.9
ruby-1.8.7.72_1,1
bison-2.4.1,1 libXmu-1.0.4,1
nasm-2.05.01,1 ruby18-bdb-0.6.5
cups-base-1.3.9_3 libXrandr-1.3.0
ncftp-3.2.2_1 samba-3.0.34,1
db41-4.1.25_4 libXrender-0.9.4_1
net-snmp-5.3.2.3screen-4.0.3_6
dev86-0.16.17 libXt-1.0.5_1 nmap-4.76
tiff-3.8.2_3
fixesproto-4.0 libcheck-0.9.6
openldap-client-2.4.15_1vsftpd-ssl-2.1.0
freetype2-2.3.7 libdnet-1.11_2
openvpn-2.0.6_9 xcb-proto-1.5
gd-2.0.35,1 libexecinfo-1.1_3
p5-Pod-Parser-1.38 xcmiscproto-1.1.2
gettext-0.17_1 libgcrypt-1.4.4
p5-SNMP_Session-1.12xextproto-7.0.5
gmake-3.81_3libgpg-error-1.7
p5-gettext-1.05_2 xf86bigfontproto-1.1.2
gnutls-2.6.4libiconv-1.11_1 pcre-7.8
xorg-macros-1.2.1
help2man-1.36.4_2 libpthread-stubs-0.1
perl-threaded-5.8.9_2 xproto-7.0.15
inputproto-1.5.0libsigsegv-2.5 pfstat-2.4
xtrans-1.2.3
isc-dhcp30-server-3.0.7_4 libtool-1.5.26 pftop-0.7_1
yasm-0.8.0
#
pkg_add with NFS
Greetings A simple question from a simple mind. Or, at least a forgetful one. I am slowly moving the computers in my SOHO to FreeBSD 8 from 7-stable. In order to be more efficient, I am using a faster server as a source and ports server. The source portion is working as designed with the slower boxes able to update simply with a make kernel, reboot, make installworld. I am exporting and then NFS mounting /usr/src, /usr/obj, and /usr/ports. I had rebuilt all of my ports on the faster computer with pagkage-recursive. I change the environment on the client box of PACKAGESITE to /usr/ports/packages/ALL but when I try pkg_add I get the error can't stat package file 'xorg'. Yes, the file xorg-7blah.tbz does show at that location. I probably am forgetting something simple but my searches have not triggered anything. Thanks Robert ___ 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: SourceForge changing file distribution scheme!
* Dmitry Marakasov (amd...@amdmi3.ru) wrote: > I've noticed that SF is changing file distribution scheme significantly, So, what do we do? May I commit the patch (+portmgr)? I believe this to be the best solution (even if a temporary one if we'll be able to resolve things with SF) as it will be clear which port uses the new scheme and there will be no variety of workarounds. The patch is still there: http://people.freebsd.org/~amdmi3/bsd.sites.mk.patch - Add MASTER_SITE_SOURCEFORGE_NEW for new scheme urls - Revive garr mirror as it's useable again -- Dmitry Marakasov . 55B5 0596 FF1E 8D84 5F56 9510 D35A 80DD F9D2 F77D amd...@amdmi3.ru ..: jabber: amd...@jabber.ruhttp://www.amdmi3.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: SourceForge changing file distribution scheme!
On Tue, Aug 11, 2009 at 8:44 PM, Dmitry Marakasov wrote: > * Dmitry Marakasov (amd...@amdmi3.ru) wrote: > >> I've noticed that SF is changing file distribution scheme significantly, > > So, what do we do? May I commit the patch (+portmgr)? I believe this to > be the best solution (even if a temporary one if we'll be able to > resolve things with SF) as it will be clear which port uses the new > scheme and there will be no variety of workarounds. > Hi, Perhaps I've lost it in this thread, but is it only a certain amount of ports affected? It appears the two SF ports I maintain hiccup a bit, but are able to eventually find the distfile. -- Glen Barber ___ 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 Port: omnetpp-3.3_3
Probably there is an error in the Makefile of omnetpp:
When I do portupgrade at the install phase the following output is shown:
---> Installing the new version via the port
===> Installing for omnetpp-3.3_3
===> omnetpp-3.3_3 depends on executable: convert - found
===> omnetpp-3.3_3 depends on executable: dot - found
===> omnetpp-3.3_3 depends on executable: doxygen - found
===> omnetpp-3.3_3 depends on executable: giftrans - found
===> omnetpp-3.3_3 depends on file: /usr/local/bin/perl5.10.0 - found
===> omnetpp-3.3_3 depends on executable: pkg-config - found
===> omnetpp-3.3_3 depends on shared library: BLT24 - found
===> omnetpp-3.3_3 depends on shared library: tcl84 - found
===> omnetpp-3.3_3 depends on shared library: tk84 - found
===> omnetpp-3.3_3 depends on shared library: glib-12.3 - found
===> omnetpp-3.3_3 depends on shared library: xml.5 - found
===> omnetpp-3.3_3 depends on shared library: xml2.5 - found
===> omnetpp-3.3_3 depends on shared library: xslt.2 - found
cp: pkg-plist: No such file or directory
*** Error code 1
Stop in /usr/ports/science/omnetpp.
*** Error code 1
Stop in /usr/ports/science/omnetpp.
*** Error code 1
Stop in /usr/ports/science/omnetpp.
** Command failed [exit code 1]: /usr/bin/script -qa
/tmp/portupgrade20090812-79645-1tpm94n-0 env UPGRADE_TOOL=portupgrade
UPGRADE_PORT=omnetpp-3.3_2 UPGRADE_PORT_VER=3.3_2 make reinstall
---> Restoring the old version
** Fix the installation problem and try again.
[Updating the pkgdb in /var/db/pkg ... - 298 packages
found (-0 +1) . done]
** Listing the failed packages (-:ignored / *:skipped / !:failed)
! science/omnetpp (omnetpp-3.3_2) (install error)
As you see the error is:
cp: pkg-plist: No such file or directory
This is produced by the Makefile 85th line:
pre-install:
@${CP} pkg-plist ${PLIST}
Probably this work when port working directory is inside
the port directory.
But when working directory is elsewhere (e.g. in my case in a different
working partition) it does not work because pkg-plist is still
in the port directory.
To correct this error I suggest the following change (tested):
pre-install:
@(cd ${PORTSDIR}/science/omnetpp;; \
${CP} pkg-plist ${PLIST} \
)
or (not tested):
pre-install:
@${CP} ${PORTSDIR}/science/omnetpp/pkg-plist ${PLIST}
I don't know if it is better to use another more elegant form to fix
this at this moment.
Having a working directory is legal and this is set putting the
following variable in /etc/make.conf
WRKDIRPREFIX= /somedir
Check it, and when you can, please update the Makefile.
Cheers,
Gabriele
___
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 Port: omnetpp-3.3_3
On Tuesday 11 August 2009 19:13:44 Gabriele Cecchetti wrote:
> Probably there is an error in the Makefile of omnetpp:
>
> When I do portupgrade at the install phase the following output is shown:
>
> ---> Installing the new version via the port
> ===> Installing for omnetpp-3.3_3
> ===> omnetpp-3.3_3 depends on executable: convert - found
> ===> omnetpp-3.3_3 depends on executable: dot - found
> ===> omnetpp-3.3_3 depends on executable: doxygen - found
> ===> omnetpp-3.3_3 depends on executable: giftrans - found
> ===> omnetpp-3.3_3 depends on file: /usr/local/bin/perl5.10.0 - found
> ===> omnetpp-3.3_3 depends on executable: pkg-config - found
> ===> omnetpp-3.3_3 depends on shared library: BLT24 - found
> ===> omnetpp-3.3_3 depends on shared library: tcl84 - found
> ===> omnetpp-3.3_3 depends on shared library: tk84 - found
> ===> omnetpp-3.3_3 depends on shared library: glib-12.3 - found
> ===> omnetpp-3.3_3 depends on shared library: xml.5 - found
> ===> omnetpp-3.3_3 depends on shared library: xml2.5 - found
> ===> omnetpp-3.3_3 depends on shared library: xslt.2 - found
> cp: pkg-plist: No such file or directory
...
> Having a working directory is legal and this is set putting the
> following variable in /etc/make.conf
> WRKDIRPREFIX= /somedir
FWIW, reproduced and ${.CURDIR} should be used (`pwd` at pre-install is
${.OBJDIR}).
--
Mel
Index: science/omnetpp/Makefile
===
RCS file: /home/ncvs/ports/science/omnetpp/Makefile,v
retrieving revision 1.12
diff -u -r1.12 Makefile
--- science/omnetpp/Makefile31 Jul 2009 13:55:36 - 1.12
+++ science/omnetpp/Makefile12 Aug 2009 06:21:49 -
@@ -82,7 +82,7 @@
@${ECHO} "WISH=wish${TK_VER}" >> ${CONFIGUREUSER}
pre-install:
- @${CP} pkg-plist ${PLIST}
+ @${CP} ${.CURDIR}/pkg-plist ${PLIST}
@(cd ${WRKSRC}; \
${FIND} -s include -type f | ${SED}
"s,^include,${INCLDIR_REL}," >> ${PLIST}; \
${FIND} -s -d include -type d | ${SED} "s,^include,@dirrm
${INCLDIR_REL}," >> ${PLIST}; \
___
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"
