Re: [RFC] New category proposal, i18n
If i18n is too cryptic or too alphanumeric, and internationalization is too long, why not go with nls? I personally think that nls is equally as cryptic as i18n or l10n. Anyone care for intlzn? It's short, should still tab-complete from in, and it may be a bit less cryptic than nls, i18n, or l10n. ___ 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
next abort of perl upgrade encountered--linux-pango security problem :-(
The saga of failures in the perl upgrade continues with the following: === linux-gtk2-2.6.10_3 depends on file: /compat/linux/usr/lib/libpango-1.0.so.0.1001.1 - not found ===Verifying install for /compat/linux/usr/lib/libpango-1.0.so.0.1001.1 in /usr/ports/x11-toolkits/linux-pango === linux-pango-1.10.2_3 has known vulnerabilities: = pango -- integer overflow. Reference: http://www.FreeBSD.org/ports/portaudit/4b172278-3f46-11de-becb-001cc0377035.html = Please update your ports tree and try again. *** Error code 1 Stop in /usr/ports/x11-toolkits/linux-pango. *** Error code 1 Stop in /usr/ports/x11-toolkits/linux-gtk2. *** Error code 1 Stop in /usr/ports/multimedia/linux-realplayer. *** Error code 1 Stop in /usr/ports/multimedia/mplayer. === make failed for multimedia/mplayer === Aborting update === Update for mplayer-0.99.11_12 failed === Aborting update === There are messages from installed ports to display, but first take a moment to review the error messages above. Then press Enter when ready to proceed. [messages omitted here --SB] === Done displaying pkg-message files === The following actions were performed: Re-installation of perl-threaded-5.10.0_3 Upgrade of ImageMagick-6.5.2.10 to ImageMagick-6.5.3.10 Upgrade of dvipdfmx-20080607_1 to dvipdfmx-20090522_1 Upgrade of git-1.6.3.2_1 to git-1.6.3.3 Upgrade of gstreamer-plugins-a52dec-0.10.11,3 to gstreamer-plugins-a52dec-0.10.12,3 Upgrade of gstreamer-plugins-bad-0.10.11,3 to gstreamer-plugins-bad-0.10.13,3 Upgrade of gstreamer-plugins-dts-0.10.11,3 to gstreamer-plugins-dts-0.10.13,3 Upgrade of gstreamer-plugins-dvd-0.10.11,3 to gstreamer-plugins-dvd-0.10.12,3 Upgrade of gstreamer-plugins-good-0.10.14,3 to gstreamer-plugins-good-0.10.15,3 Upgrade of gstreamer-plugins-libpng-0.10.14,3 to gstreamer-plugins-libpng-0.10.15,3 Upgrade of gstreamer-plugins-mad-0.10.11,3 to gstreamer-plugins-mad-0.10.12,3 Upgrade of gstreamer-plugins-ugly-0.10.11,3 to gstreamer-plugins-ugly-0.10.12,3 Upgrade of gstreamer-plugins-xvid-0.10.11,3 to gstreamer-plugins-xvid-0.10.13,3 hellas# There doesn't seem to be a more recent version of the x11-toolkits/linux-pango port available. What is the best way to proceed? Will a portmaster -fv x11-toolkits/linux-pango do the job for now? (I'm not too worried about the security bug for the moment. Although I use mplayer to play files, they don't generally involve .png files, and I don't use mplayer to play streaming files.) Please copy me in on responses, otherwise I won't see them till the next freebsd-ports digest is sent out. Thanks! Scott Bennett, Comm. ASMELG, CFIAG ** * Internet: bennett at cs.niu.edu * ** * A well regulated and disciplined militia, is at all times a good * * objection to the introduction of that bane of all free governments * * -- a standing army. * *-- Gov. John Hancock, New York Journal, 28 January 1790 * ** ___ 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: next abort of perl upgrade encountered--linux-pango security problem :-(
В Thu, 25 Jun 2009 01:21:19 -0500 (CDT) Scott Bennett benn...@cs.niu.edu пишет: SB The saga of failures in the perl upgrade continues with the SB following: SB SB === linux-gtk2-2.6.10_3 depends on SB file: /compat/linux/usr/lib/libpango-1.0.so.0.1001.1 - not found SB ===Verifying install SB for /compat/linux/usr/lib/libpango-1.0.so.0.1001.1 SB in /usr/ports/x11-toolkits/linux-pango === linux-pango-1.10.2_3 SB has known vulnerabilities: = pango -- integer overflow. Reference: SB http://www.FreeBSD.org/ports/portaudit/4b172278-3f46-11de-becb-001cc0377035.html SB = Please update your ports tree and try again. *** Error code 1 [skipped] SB SB There doesn't seem to be a more recent version of the SB x11-toolkits/linux-pango port available. What is the best way to SB proceed? Will a portmaster -fv x11-toolkits/linux-pango do the SB job for now? (I'm not too worried about the security bug for the SB moment. Although I use mplayer to play files, they don't generally SB involve .png files, and I don't use mplayer to play streaming SB files.) Please copy me in on responses, otherwise I won't see them SB till the next freebsd-ports digest is sent out. Thanks! SB SB SB Scott Bennett, Comm. ASMELG, CFIAG 1) deinstall portaudit 2) upgrate all ports 3) install portaudit if you need it or 1)rm /var/db/portaudit/auditfile.tbz 2) upgrate all ports 3) portaudit -F -- wbr, tiger ___ 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: next abort of perl upgrade encountered--linux-pango security problem :-(
В Thu, 25 Jun 2009 09:37:52 +0300 Sergey V. Dyatko sergey.dya...@gmail.com пишет: SVD В Thu, 25 Jun 2009 01:21:19 -0500 (CDT) SVD Scott Bennett benn...@cs.niu.edu пишет: SVD SVD SB The saga of failures in the perl upgrade continues with SVD SB the following: SVD SB SVD SB === linux-gtk2-2.6.10_3 depends on SVD SB file: /compat/linux/usr/lib/libpango-1.0.so.0.1001.1 - not SVD SB found ===Verifying install SVD SB for /compat/linux/usr/lib/libpango-1.0.so.0.1001.1 SVD SB in /usr/ports/x11-toolkits/linux-pango === SVD SB linux-pango-1.10.2_3 has known vulnerabilities: = pango -- SVD SB integer overflow. Reference: SVD SB http://www.FreeBSD.org/ports/portaudit/4b172278-3f46-11de-becb-001cc0377035.html SVD SB = Please update your ports tree and try again. *** Error code SVD SB 1 SVD [skipped] SVD SB SVD SB There doesn't seem to be a more recent version of the SVD SB x11-toolkits/linux-pango port available. What is the best way SVD SB to proceed? Will a portmaster -fv x11-toolkits/linux-pango SVD SB do the job for now? (I'm not too worried about the security SVD SB bug for the moment. Although I use mplayer to play files, SVD SB they don't generally involve .png files, and I don't use SVD SB mplayer to play streaming files.) Please copy me in on SVD SB responses, otherwise I won't see them till the next SVD SB freebsd-ports digest is sent out. Thanks! SVD SB SVD SB SVD SB Scott Bennett, Comm. ASMELG, SVD SB CFIAG SVD 1) deinstall portaudit SVD 2) upgrate all ports SVD 3) install portaudit if you need it SVD SVD or SVD SVD 1)rm /var/db/portaudit/auditfile.tbz SVD 2) upgrate all ports SVD 3) portaudit -F SVD or set environment variable DISABLE_VULNERABILITIES and upgrade port(s) -- wbr, tiger ___ 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: built with OLD dependency, take 2
Peter Clark cla...@mtmary.edu writes: Hello, I am not sure where to ask this question so I am going to start here, if this is not the correct place any direction to where I should as would be appreciated. I have 2 Freebsd 7.2p1 fresh installs. I have installed a number of ports while trying to configure them to their final configuration (everything installed is from ports). Weekly I cvsup my ports and run portmanager -u. On both of these boxes I now have a missing port and ones listed as being built with an OLD dependency. Box 1: snip of portmanager -u: 00020 have:cyrus-sasl-2.1.23 /security/cyrus-sasl2 CURRENT 00023 have:openldap-sasl-server-2.4.16_1 /net/openldap24-server CURRENT 00025 have:postfix-2.6.2_1,1 /mail/postfix built with OLD dependency: openldap-client-2.4.16 00027 :openldap-client-2.4.16 /net/openldap24-client MISSING 00034 have:openldap-sasl-client-2.4.16 /net/openldap24-sasl-client CURRENT skipping postfix-2.6.2_1,1 /mail/postfix until dependency openldap-client-2.4.16 updated skipping openldap-client-2.4.16 /net/openldap24-client marked IGNORE reason: conflicts with another installed port Box 2: snip of portmanager -u: 00024 have:openldap-sasl-server-2.4.16_1 /net/openldap24-server CURRENT 00031 have:apache-2.2.11_7 /www/apache22 built with OLD dependency: openldap-client-2.4.16 00032 :openldap-client-2.4.16 /net/openldap24-client MISSING 00033 have:php5-5.2.9 /lang/php5CURRENT 00035 have:php5-ldap-5.2.9 /net/php5-ldap built with OLD dependency: openldap-client-2.4.16 00042 have:phpldapadmin-1.1.0.7,1 /net/phpldapadmin CURRENT 00050 have:openldap-sasl-client-2.4.16 /net/openldap24-sasl-client CURRENT skipping apache-2.2.11_7 /www/apache22 until dependency openldap-client-2.4.16 updated skipping openldap-client-2.4.16 /net/openldap24-client marked IGNORE reason: conflicts with another installed port skipping php5-ldap-5.2.9 /net/php5-ldap until dependency openldap-client-2.4.16 updated postfix is built with openldap but not sasl2 apache is built with ldap and authnz_ldap On both of the boxes the offender seems to be openldap-client-2.4.16. I installed the sasl-server version of openldap which in turn installed the openldap-sasl-client. I am not sure why postfix, apache22 and php5-ldap are having a problem with the sasl vs non sasl versions. I think that the sasl client and the regular client write to the same place though they conflict with each other. Is there a way to resolve this? I'm not an expert here but since nobody has responded so far give me a try. If you need an openldap-sasl-client then the best way is to define WANT_OPENLDAP_SASL=YES at /etc/make.conf. Then all other ports which use openldap should use (have a dependency, check for existence, etc.) openldap-sasl port but not plain openldap. I'd advice you to remove all ports that depends upon openldap ports, add the abovementioned line to /etc/make.conf and reinstall the needed ports. WBR -- bsam ___ 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: next abort of perl upgrade encountered--linux-pango security problem :-(
On Thu, 25 Jun 2009 09:37:52 +0300 Sergey V. Dyatko sergey.dya...@gmail.com wrote: 1) deinstall portaudit 2) upgrate all ports 3) install portaudit if you need it or 1)rm /var/db/portaudit/auditfile.tbz 2) upgrate all ports 3) portaudit -F Way too much trouble and potentially dangerous. Enter this in the /etc/make.conf file: # Pango ..if $(.CURDIR:M*/x11-toolkits/linux-pango) DISABLE_VULNERABILITIES=yes ..endif This way, the DISABLE_VULNERABILITIES=yes will only effect one port. -- Jerry ges...@yahoo.com Freedom from incrustation of grime is contiguous to rectitude. ___ 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: [RFC] New category proposal, i18n
2009/6/25 per...@pluto.rain.com: If i18n is too cryptic or too alphanumeric, and internationalization is too long, why not go with nls? I personally think that nls is equally as cryptic as i18n or l10n. Anyone care for intlzn? It's short, should still tab-complete from in, and it may be a bit less cryptic than nls, i18n, or l10n. I was thinking intl, but your suggestion's better. Chris -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in a mailing list? ___ 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: vim ports broken.
Carlos A. M. dos Santos wrote:
Choosing % to differentiate it, however, was a bad idea. It would
be better to use a simple underscore.
Why is % any worse than an underscore? As I explained earlier, fetch has no
problem dealing with it. The errors people were posting are server-side,
ftp.freebsd.org has no problems handling it.
POLA: users get surprised by the Bad Request answer and think that
the package is broken. So they complain at -ports, generating lengthy
email threads.
I have another suggestion: why not tell it that this specific patch file
should be fetched from the FreeBSD server and not try all the other vim
mirror sites. We have a mechanism to do so, which seems appropriate here.
Johan
--- Makefile.orig 2009-06-25 10:24:08.0 +0200
+++ Makefile2009-06-25 10:21:52.0 +0200
@@ -16,7 +16,7 @@
DISTFILES= ${RELEASE}${EXTRACT_SUFX}
PATCH_SITES= ${MASTER_SITES:S|unix|patches/${PORTVERSION:C/\.[0-9a-z]*$//}|}\
- ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/obrien/
+
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/obrien/:local
PATCHFILES!= /usr/bin/jot -s -w ${PORTVERSION:C/\.[0-9]*$//}.%03d \
${PATCHLEVEL} 1 ${PATCHLEVEL}
# bits to remove
@@ -27,7 +27,7 @@
.for p in ${BADPATCHES}
PATCHFILES:= ${PATCHFILES:N7.2.${p}}
.endfor
-PATCHFILES:= ${PATCHFILES:S/041/041%/}
+PATCHFILES:= ${PATCHFILES:S/041/041%:local/}
MAINTAINER?= obr...@freebsd.org
COMMENT?= Vi workalike, with many additional features
pgpFFuM2zMmhp.pgp
Description: PGP signature
Re: next abort of perl upgrade encountered--linux-pango security problem :-(
В Thu, 25 Jun 2009 04:12:06 -0400 Jerry ges...@yahoo.com пишет: J On Thu, 25 Jun 2009 09:37:52 +0300 J Sergey V. Dyatko sergey.dya...@gmail.com wrote: J J 1) deinstall portaudit J 2) upgrate all ports J 3) install portaudit if you need it J J or J J 1)rm /var/db/portaudit/auditfile.tbz J 2) upgrate all ports J 3) portaudit -F J J Way too much trouble and potentially dangerous. I agree with you but Scott wrote I'm not too worried about the security bug for the moment. So it must works J Enter this in the /etc/make.conf file: J J # Pango J ..if $(.CURDIR:M*/x11-toolkits/linux-pango) J DISABLE_VULNERABILITIES=yes J ..endif yep, that is rightest way (IHMO) J J This way, the DISABLE_VULNERABILITIES=yes will only effect one port. J J -- --- Sergey V Dyatko aka tiger | sergey.dya...@gmail.com /\ ASCII Ribbon Campaign | FreeBSD Since 4.x \ / - NO HTML/RTF in e-mail | http://tiger.bsd.by X - NO Word docs in e-mail | XMPP: ti...@jabber.org.by / \ --- ___ 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
cannot do pkg_add -f package
Hello List,
I downloaded a package from pointyhat:
http://pointyhat.freebsd.org/errorlogs/i386-8-packages-latest/databases/fpc-postgres-2.2.4.tbz
And can not do a pkg_add -f of this package:
-
# uname -a
FreeBSD moosi 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon Jun 22 21:04:20 MSD 2009
r...@moosi:/usr/obj/usr/src/sys/MOOSI i386
# pkg_add -fv fpc-postgres-2.2.4.tbz
Requested space: 247K bytes, free space: 2606M bytes in /var/tmp/instmp.iunpHr
pkg_add: can't stat package file
'/usr/home/bsam/download/All/postgresql-client-8.2.13.tbz'
Package 'fpc-postgres-2.2.4' depends on 'libiconv-1.13' with
'converters/libiconv' origin.
- already installed.
Package 'fpc-postgres-2.2.4' depends on 'gettext-0.17_1' with 'devel/gettext'
origin.
- already installed.
Package 'fpc-postgres-2.2.4' depends on 'postgresql-client-8.2.13' with
'databases/postgresql82-client' origin.
pkg_add: could not find package postgresql-client-8.2.13 (proceeding anyway)
extract: Package name is fpc-postgres-2.2.4
extract: CWD to /usr/local
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/Package.fpc
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/dllist.ppu
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/dllistdyn.ppu
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres.ppu
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3.ppu
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3dyn.ppu
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/dllist.o
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/dllistdyn.o
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres.o
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3.o
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3dyn.o
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/libpdllist.a
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/libpdllistdyn.a
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres.a
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres3.a
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres3dyn.a
extract: CWD to .
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/Package.fpc: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/dllist.ppu: Cannot stat: No such
file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/dllistdyn.ppu: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres.ppu: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3.ppu: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3dyn.ppu: Cannot stat:
No such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/dllist.o: Cannot stat: No such
file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/dllistdyn.o: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres.o: Cannot stat: No such
file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3.o: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3dyn.o: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/libpdllist.a: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/libpdllistdyn.a: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres.a: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres3.a: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres3dyn.a: Cannot stat:
No such file or directory
tar: Error exit delayed from previous errors.
Attempting to record package into /var/db/pkg/fpc-postgres-2.2.4..
mv: rename ./+DESC to /var/db/pkg/fpc-postgres-2.2.4/+DESC: No such file or
directory
pkg_add: leave_playpen: can't chdir back to ''
# ls -l /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres
ls: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres: No such file or
directory
#
-
The relevant part from ktrace/kdump seems to be:
-
55129 pkg_add GIO fd 1 wrote 27 bytes
extract: CWD to /usr/local
55129 pkg_add RET write 27/0x1b
55129 pkg_add CALL lstat(0x2840d110,0xbfbba3e8)
55129 pkg_add NAMI /usr
55129 pkg_add STRU struct stat {dev=106, ino=2, mode=drwxr-xr-x , nlink=18,
uid=0, gid=0, rdev=3008, atime=1245917171, stime=1245688372, ctime=1245688391,
birthtime=1222160241, size=512, blksize=4096, blocks=4, flags=0x0 }
55129 pkg_add RET lstat 0
55129 pkg_add CALL lstat(0x2840d110,0xbfbba3e0)
55129 pkg_add NAMI /usr
55129 pkg_add STRU struct stat {dev=106, ino=2, mode=drwxr-xr-x , nlink=18,
uid=0, gid=0, rdev=3008,
Re: vim ports broken.
Johan van Selst wrote:
Carlos A. M. dos Santos wrote:
Choosing % to differentiate it, however, was a bad idea. It would
be better to use a simple underscore.
Why is % any worse than an underscore? As I explained earlier, fetch has no
problem dealing with it. The errors people were posting are server-side,
ftp.freebsd.org has no problems handling it.
POLA: users get surprised by the Bad Request answer and think that
the package is broken. So they complain at -ports, generating lengthy
email threads.
I have another suggestion: why not tell it that this specific patch file
should be fetched from the FreeBSD server and not try all the other vim
mirror sites. We have a mechanism to do so, which seems appropriate here.
Johan
--- Makefile.orig 2009-06-25 10:24:08.0 +0200
+++ Makefile2009-06-25 10:21:52.0 +0200
@@ -16,7 +16,7 @@
DISTFILES= ${RELEASE}${EXTRACT_SUFX}
PATCH_SITES= ${MASTER_SITES:S|unix|patches/${PORTVERSION:C/\.[0-9a-z]*$//}|}\
- ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/obrien/
+
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/obrien/:local
PATCHFILES!= /usr/bin/jot -s -w ${PORTVERSION:C/\.[0-9]*$//}.%03d \
${PATCHLEVEL} 1 ${PATCHLEVEL}
# bits to remove
@@ -27,7 +27,7 @@
.for p in ${BADPATCHES}
PATCHFILES:= ${PATCHFILES:N7.2.${p}}
.endfor
-PATCHFILES:= ${PATCHFILES:S/041/041%/}
+PATCHFILES:= ${PATCHFILES:S/041/041%:local/}
MAINTAINER?= obr...@freebsd.org
COMMENT?= Vi workalike, with many additional features
I figured there was a mechanism for this, but I honestly did not look
into it. I would suggest submitting this as a PR so the maintainer see's
it, as he has yet to comment on this thread.
--
Frank Laszlo
lasz...@freebsd.org
FreeBSD Ports Committer
___
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: cannot do pkg_add -f package
Boris Samorodov wrote:
Hello List,
I downloaded a package from pointyhat:
http://pointyhat.freebsd.org/errorlogs/i386-8-packages-latest/databases/fpc-postgres-2.2.4.tbz
And can not do a pkg_add -f of this package:
-
# uname -a
FreeBSD moosi 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon Jun 22 21:04:20 MSD 2009
r...@moosi:/usr/obj/usr/src/sys/MOOSI i386
# pkg_add -fv fpc-postgres-2.2.4.tbz
Requested space: 247K bytes, free space: 2606M bytes in /var/tmp/instmp.iunpHr
pkg_add: can't stat package file
'/usr/home/bsam/download/All/postgresql-client-8.2.13.tbz'
Package 'fpc-postgres-2.2.4' depends on 'libiconv-1.13' with
'converters/libiconv' origin.
- already installed.
Package 'fpc-postgres-2.2.4' depends on 'gettext-0.17_1' with 'devel/gettext'
origin.
- already installed.
Package 'fpc-postgres-2.2.4' depends on 'postgresql-client-8.2.13' with
'databases/postgresql82-client' origin.
pkg_add: could not find package postgresql-client-8.2.13 (proceeding anyway)
extract: Package name is fpc-postgres-2.2.4
extract: CWD to /usr/local
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/Package.fpc
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/dllist.ppu
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/dllistdyn.ppu
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres.ppu
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3.ppu
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3dyn.ppu
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/dllist.o
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/dllistdyn.o
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres.o
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3.o
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3dyn.o
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/libpdllist.a
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/libpdllistdyn.a
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres.a
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres3.a
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres3dyn.a
extract: CWD to .
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/Package.fpc: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/dllist.ppu: Cannot stat: No such
file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/dllistdyn.ppu: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres.ppu: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3.ppu: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3dyn.ppu: Cannot stat:
No such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/dllist.o: Cannot stat: No such
file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/dllistdyn.o: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres.o: Cannot stat: No such
file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3.o: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3dyn.o: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/libpdllist.a: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/libpdllistdyn.a: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres.a: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres3.a: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres3dyn.a: Cannot stat:
No such file or directory
tar: Error exit delayed from previous errors.
Attempting to record package into /var/db/pkg/fpc-postgres-2.2.4..
mv: rename ./+DESC to /var/db/pkg/fpc-postgres-2.2.4/+DESC: No such file or
directory
pkg_add: leave_playpen: can't chdir back to ''
# ls -l /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres
ls: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres: No such file or
directory
#
-
The relevant part from ktrace/kdump seems to be:
-
55129 pkg_add GIO fd 1 wrote 27 bytes
extract: CWD to /usr/local
55129 pkg_add RET write 27/0x1b
55129 pkg_add CALL lstat(0x2840d110,0xbfbba3e8)
55129 pkg_add NAMI /usr
55129 pkg_add STRU struct stat {dev=106, ino=2, mode=drwxr-xr-x , nlink=18,
uid=0, gid=0, rdev=3008, atime=1245917171, stime=1245688372, ctime=1245688391,
birthtime=1222160241, size=512, blksize=4096, blocks=4, flags=0x0 }
55129 pkg_add RET lstat 0
55129 pkg_add CALL lstat(0x2840d110,0xbfbba3e0)
55129 pkg_add NAMI /usr
55129 pkg_add STRU struct stat {dev=106, ino=2, mode=drwxr-xr-x , nlink=18,
uid=0, gid=0,
Re: cannot do pkg_add -f package
On Thu, 25 Jun 2009 08:30:01 -0400 Frank J. Laszlo wrote:
Boris Samorodov wrote:
I downloaded a package from pointyhat:
http://pointyhat.freebsd.org/errorlogs/i386-8-packages-latest/databases/fpc-postgres-2.2.4.tbz
And can not do a pkg_add -f of this package:
-
# uname -a
FreeBSD moosi 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Mon Jun 22 21:04:20 MSD
2009 r...@moosi:/usr/obj/usr/src/sys/MOOSI i386
# pkg_add -fv fpc-postgres-2.2.4.tbz
Requested space: 247K bytes, free space: 2606M bytes in
/var/tmp/instmp.iunpHr
pkg_add: can't stat package file
'/usr/home/bsam/download/All/postgresql-client-8.2.13.tbz'
Package 'fpc-postgres-2.2.4' depends on 'libiconv-1.13' with
'converters/libiconv' origin.
- already installed.
Package 'fpc-postgres-2.2.4' depends on 'gettext-0.17_1' with
'devel/gettext' origin.
- already installed.
Package 'fpc-postgres-2.2.4' depends on 'postgresql-client-8.2.13' with
'databases/postgresql82-client' origin.
pkg_add: could not find package postgresql-client-8.2.13 (proceeding
anyway)
[*] The warning was ignored
extract: Package name is fpc-postgres-2.2.4
extract: CWD to /usr/local
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/Package.fpc
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/dllist.ppu
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/dllistdyn.ppu
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres.ppu
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3.ppu
extract:
/usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3dyn.ppu
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/dllist.o
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/dllistdyn.o
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres.o
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3.o
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3dyn.o
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/libpdllist.a
extract:
/usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/libpdllistdyn.a
extract: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres.a
extract:
/usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres3.a
extract:
/usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres3dyn.a
extract: CWD to .
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/Package.fpc: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/dllist.ppu: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/dllistdyn.ppu: Cannot stat:
No such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres.ppu: Cannot stat:
No such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3.ppu: Cannot stat:
No such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3dyn.ppu: Cannot
stat: No such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/dllist.o: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/dllistdyn.o: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres.o: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3.o: Cannot stat: No
such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/postgres3dyn.o: Cannot stat:
No such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/libpdllist.a: Cannot stat:
No such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/libpdllistdyn.a: Cannot
stat: No such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres.a: Cannot stat:
No such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres3.a: Cannot
stat: No such file or directory
tar: lib/fpc/2.2.4/units/i386-freebsd/postgres/libppostgres3dyn.a: Cannot
stat: No such file or directory
tar: Error exit delayed from previous errors.
Attempting to record package into /var/db/pkg/fpc-postgres-2.2.4..
mv: rename ./+DESC to /var/db/pkg/fpc-postgres-2.2.4/+DESC: No such file or
directory
pkg_add: leave_playpen: can't chdir back to ''
# ls -l /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres
ls: /usr/local/lib/fpc/2.2.4/units/i386-freebsd/postgres: No such file or
directory
#
-
The relevant part from ktrace/kdump seems to be:
-
55129 pkg_add GIO fd 1 wrote 27 bytes
extract: CWD to /usr/local
55129 pkg_add RET write 27/0x1b
55129 pkg_add CALL lstat(0x2840d110,0xbfbba3e8)
55129 pkg_add NAMI /usr
55129 pkg_add STRU struct stat {dev=106, ino=2, mode=drwxr-xr-x ,
nlink=18, uid=0, gid=0, rdev=3008, atime=1245917171, stime=1245688372,
Re: [RFC] New category proposal, i18n
per...@pluto.rain.com wrote: If i18n is too cryptic or too alphanumeric, and internationalization is too long, why not go with nls? I personally think that nls is equally as cryptic as i18n or l10n. Anyone care for intlzn? It's short, should still tab-complete from in, and it may be a bit less cryptic than nls, i18n, or l10n. If I may be so bold as to present a democratic outcome. To help settle the matter please vote on this issue within 48 hours. http://www.micropoll.com/akira/mpview/615850-178803 ___ 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
php5-readline-5.2.10 patch compile error
Hi, i've upgraded php to 5.2.10 with portupgrade, php5-readline-5.2.10 won't compile. Here's the error: --- Upgrading 'php5-readline-5.2.9' to 'php5-readline-5.2.10' (devel/php5-readline) OK? [yes] --- Build of devel/php5-readline started at: Thu, 25 Jun 2009 16:09:16 +0200 --- Building '/usr/ports/devel/php5-readline' === Cleaning for php5-readline-5.2.10 === Extracting for php5-readline-5.2.10 = MD5 Checksum OK for php-5.2.10.tar.bz2. = SHA256 Checksum OK for php-5.2.10.tar.bz2. === Patching for php5-readline-5.2.10 === Applying FreeBSD patches for php5-readline-5.2.10 1 out of 3 hunks failed--saving rejects to config.m4.rej = Patch patch-config.m4 failed to apply cleanly. *** Error code 1 Stop in /usr/ports/devel/php5-readline. ** Command failed [exit code 1]: /usr/bin/script -qa /tmp/portupgrade20090625-75944-1w6ribe-0 env UPGRADE_TOOL=portupgrade UPGRADE_PORT=php5-readline-5.2.9 UPGRADE_PORT_VER=5.2.9 make ** Fix the problem and try again. --- Build of devel/php5-readline ended at: Thu, 25 Jun 2009 16:09:21 +0200 (consumed 00:00:05) --- Upgrade of devel/php5-readline ended at: Thu, 25 Jun 2009 16:09:21 +0200 (consumed 00:00:31) And the config.m4.rej file: *** *** 50,55 -L$READLINE_DIR/$PHP_LIBDIR $PHP_READLINE_LIBS ]) PHP_CHECK_LIBRARY(history, add_history, [ PHP_ADD_LIBRARY_WITH_PATH(history, $READLINE_DIR/$PHP_LIBDIR, READLINE_SHARED_LIBADD) --- 48,60 -L$READLINE_DIR/$PHP_LIBDIR $PHP_READLINE_LIBS ]) + PHP_CHECK_LIBRARY(readline, rl_completion_matches, + [ + AC_DEFINE(HAVE_RL_COMPLETION_MATCHES, 1, [ ]) + ],[],[ + -L$READLINE_DIR/$PHP_LIBDIR $PHP_READLINE_LIBS + ]) + PHP_CHECK_LIBRARY(history, add_history, [ PHP_ADD_LIBRARY_WITH_PATH(history, $READLINE_DIR/$PHP_LIBDIR, READLINE_SHARED_LIBADD) I'm on a FreeBSD 7.2-RELEASE-p1 #0. Any clue? Thanks Andrea 'simplex' Zulato ___ 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
Honoring NOPORTDOCS with GNU_CONFIGURE?
Is there a standard way to write ports which use GNU_CONFIGURE to follow NOPORTDOCS? Ideally it'd be something as simple as setting --docdir=NULL or similar, and even more ideally by having bsd.port.mk taking care of that. :-) -- Kirk Strauser ___ 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: Honoring NOPORTDOCS with GNU_CONFIGURE?
On Thursday 25 June 2009 09:57:52 am you wrote: i think that you will could use CONFIGURE_ARGS But what args would you actually use? How do you tell autotools not to install documentation at all? -- Kirk Strauser ___ 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: Honoring NOPORTDOCS with GNU_CONFIGURE?
On Thu, Jun 25, 2009 at 09:40:42AM -0500, Kirk Strauser wrote:
Is there a standard way to write ports which use GNU_CONFIGURE to follow
NOPORTDOCS? Ideally it'd be something as simple as setting --docdir=NULL or
similar, and even more ideally by having bsd.port.mk taking care of that. :-)
Not really. What I usually do is have a post-patch: target that
does a REINPLACE_CMD on all the Makefile.in's found in the port's
directpry and just removes the install-doc target; something like:
.ifdef(NOPORTDOCS)
@${REINPLACE_CMD} -E -e 's/ install-docDATA/ /; s/^(SUBDIRS.+)doc/\1/' \
${WRKSRC}/Makefile.in
@${REINPLACE_CMD} -E -e 's/([^n])install-examplesDATA/\1/' \
${WRKSRC}/tools/Makefile.in
.endif
This is taken from the security/stunnel port; you may need to fit it
for your specific port's needs, or, if there are many Makefile.in files,
use ${FIND} | ${XARGS} to process them all at once.
G'luck,
Peter
--
Peter Pentchev r...@ringlet.netr...@space.bgr...@freebsd.org
PGP key:http://people.FreeBSD.org/~roam/roam.key.asc
Key fingerprint FDBA FD79 C26F 3C51 C95E DF9E ED18 B68D 1619 4553
Hey, out there - is it *you* reading me, or is it someone else?
pgpn3xqcd84du.pgp
Description: PGP signature
Re: Honoring NOPORTDOCS with GNU_CONFIGURE?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Kirk Strauser wrote: Is there a standard way to write ports which use GNU_CONFIGURE to follow NOPORTDOCS? Ideally it'd be something as simple as setting --docdir=NULL or similar, and even more ideally by having bsd.port.mk taking care of that. :-) Hi Kirk, I did this for some of the ports that I maintain. Have a look at the freshports.org page for a commit to graphics/GraphicsMagick last year: http://is.gd/1daY4 I modified the Makefile.in at the top level to remove dependencies on install-docDATA and install-data-html, and that did the trick. Cheers, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKQ5mj0sRouByUApARAmyLAJ9KZWZEsM+OvN7Wy1vqxy0L7hLNsACgppSI hmnMAEWQ9JrKWlrza8hi92Q= =MzYT -END PGP SIGNATURE- ___ 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: Help test aqbanking-4.0.0 (especially with gnucash)
I picked up the new ports: gnucash-2.2.9_2 aqbanking-4.1.0 gwenhywfar-3.9.0 libgmp-4.3.1 guile-1.8.6_1 goffice-0.7.7 libgsf-1.14.14 and was able to build gnucash and aqbanking together successfully; I am able to do ofx operations (get statements) so it seems to work. I think there is some minor issue with regard to money market accounts (specifically, how the account type is represented within aqbanking) but I have patches to send upstream for it. Thanks for putting together the patches for the update, and thanks to amdmi3 for the commits. -- G. Paul Ziemba FreeBSD unix: 9:01AM up 12 days, 6:34, 16 users, load averages: 1.24, 1.18, 1.34 ___ 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: [REPOST] problem upgrading perl
Scott Bennett wrote: On Tue, 23 Jun 2009 10:30:11 -0700 Doug Barton do...@freebsd.org wrote: There ought to be an automated way to deal with the package issue that causes the failure of the entire update run just because it wants a human to type make deinstall make reinstall. Sorry I wasn't clear, the inherent problem I described is with perl, not with the ports. Because perl stores its libraries in a file hierarchy based on version number (arguably, a feature) when you do a straight upgrade from one version of perl to another IME the only really good way to do that is to make a list of perl-related stuff you have installed, delete everything, and reinstall. For those that only have a few libraries installed using portmaster/portupgrade -r will probably work, and is certainly worth a try. Have you tried using the -x option to exclude it? You can also use the -i option, although for a lot of ports that can get annoying. I had not, thanks to my having misread something in the portmaster man page. If you have any suggestions for improving the text I'm open to them. However, since reading your reply, I have tried (without -R) # nice +18 portmaster -x perl-threaded-5.10.0 -rv perl-threaded-5.10.0_3 If this is a literal copy of what you did I'm surprised it worked since you've placed the -v option between the -r and its argument. which did rebuild perl Yes, I just checked the code and portmaster does not check the -x argument for the main port specified in the command line. I'll take a look at that. (along with many other already rebuilt ports, of course). At this moment, I have # nice +18 portmaster -x perl-threaded-5.10.0_3 -R -rv perl-threaded-5.10.0_3 running, and it is currently rebuilding perl yet again. So the -x option appears to be useless, at least in this context. You might want to be a little more careful with your adjectives. My feelings aren't hurt but when you're asking for help, especially for something you're not paying anything for, words like useless tend not to make you any friends. I began using FreeBSD at 5.2.1. Along the way, my other complaints have largely been fixed, but the ports subsystem remains to this day the weakest part of all of FreeBSD. I realize that the problem of coordinating the installation and maintenance of such a widely diverse body of ports and packages is a complex one, Having spent a non-trivial amount of time in the bowels of the ports system I would argue that complex is a dramatic understatement. but the problems the current tools, dependency lists, Makefiles, etc. present to the user are often insoluble by anyone but an expert in the internal workings of each of the pieces of the subsystem. The packages subsystem is in about as bad shape, and in spite of the degree to which the two are intertwined, they really do not play nicely together. Once again, being more careful with your rhetoric would go a long way here. This is a volunteer project, and no one would argue that there is nothing left to improve. Feel free to roll up your sleeves and get to work. :) 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: vim ports broken.
Johan van Selst wrote:
I have another suggestion: why not tell it that this specific patch file
should be fetched from the FreeBSD server and not try all the other vim
mirror sites. We have a mechanism to do so, which seems appropriate here.
I was thinking exactly this, but never got around to writing it.
Thanks..
Johan
--- Makefile.orig 2009-06-25 10:24:08.0 +0200
+++ Makefile2009-06-25 10:21:52.0 +0200
@@ -16,7 +16,7 @@
DISTFILES= ${RELEASE}${EXTRACT_SUFX}
PATCH_SITES= ${MASTER_SITES:S|unix|patches/${PORTVERSION:C/\.[0-9a-z]*$//}|}\
- ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/obrien/
+
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/local-distfiles/obrien/:local
PATCHFILES!= /usr/bin/jot -s -w ${PORTVERSION:C/\.[0-9]*$//}.%03d \
${PATCHLEVEL} 1 ${PATCHLEVEL}
# bits to remove
@@ -27,7 +27,7 @@
.for p in ${BADPATCHES}
PATCHFILES:= ${PATCHFILES:N7.2.${p}}
.endfor
-PATCHFILES:= ${PATCHFILES:S/041/041%/}
+PATCHFILES:= ${PATCHFILES:S/041/041%:local/}
MAINTAINER?= obr...@freebsd.org
COMMENT?= Vi workalike, with many additional features
--
1024D/DB9B8C1C B90B FBC3 A3A1 C71A 8E70 3F8C 75B8 8FFB DB9B 8C1C
Philip M. Gollucci (pgollu...@p6m7g8.com) c: 703.336.9354
Consultant - P6M7G8 Inc.http://p6m7g8.net
Senior Sys Admin- RideCharge, Inc. http://ridecharge.com
Contractor - PositiveEnergyUSA http://positiveenergyusa.com
ASF Member - Apache Software Foundation http://apache.org
FreeBSD Committer - FreeBSD Foundation http://freebsd.org
Work like you don't need the money,
love like you'll never get hurt,
and dance like nobody's watching.
___
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: [RFC] New category proposal, i18n
Friday will be one week for the topic, at which point I will take on the next leg of the battle, which is making the pitch to portmgr. Thomas On 25/06/2009, Mark Foster m...@foster.cc wrote: per...@pluto.rain.com wrote: If i18n is too cryptic or too alphanumeric, and internationalization is too long, why not go with nls? I personally think that nls is equally as cryptic as i18n or l10n. Anyone care for intlzn? It's short, should still tab-complete from in, and it may be a bit less cryptic than nls, i18n, or l10n. If I may be so bold as to present a democratic outcome. To help settle the matter please vote on this issue within 48 hours. http://www.micropoll.com/akira/mpview/615850-178803 ___ 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 -- Sent from my mobile device Thomas Abthorpe, FreeBSD Ports Committer tabtho...@freebsd.org, http://people.freebsd.org/~tabthorpe ___ 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: garr sourceforge mirror is broken [Was: Re: Checksum mismatch]
* Dmitry Marakasov (amd...@amdmi3.ru) wrote: = Attempting to fetch from http://garr.dl.sourceforge.net/sourceforge/netpbm/. netpbm-10.26.62.tgz 100% of 2485 kB 379 kBps === Extracting for netpbm-10.26.62 = MD5 Checksum mismatch for netpbm-10.26.62.tgz. = SHA256 Checksum mismatch for netpbm-10.26.62.tgz. I've commented the mirror out for now. The mirror seems to be fixed. At least mesalib and netpbm witch were broken before now download correctly. It still doesn't seem to be in SF's list of mirrors, but we may consider turning it back on. -- 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
INDEX files stale on www.FreeBSD.org
The default source for ports 'make fetchindex' (MASTER_SITE_INDEX) is http://www.FreeBSD.org/ports/ The ports INDEX files at that location are stale. They were last updated about 4 days ago. ozsrv02 fetch http://www.freebsd.org/ports/INDEX-6.bz2 \ http://www.freebsd.org/ports/INDEX-7.bz2 \ http://www.freebsd.org/ports/INDEX-8.bz2 ozsrv02 TZ=UTC ls -l INDEX-[6-8].bz2 -rw-r--r-- 1 john john 1287726 Jun 22 09:44 INDEX-6.bz2 -rw-r--r-- 1 john john 1287641 Jun 22 10:08 INDEX-7.bz2 -rw-r--r-- 1 john john 1287319 Jun 22 10:33 INDEX-8.bz2 -- John Marshall pgp7SA4pHA9Px.pgp Description: PGP signature
Re: [RFC] New category proposal, i18n
On Thu, Jun 25, 2009 at 5:24 AM, Chris Reesutis...@googlemail.com wrote: 2009/6/25 per...@pluto.rain.com: If i18n is too cryptic or too alphanumeric, and internationalization is too long, why not go with nls? I personally think that nls is equally as cryptic as i18n or l10n. Anyone care for intlzn? It's short, should still tab-complete from in, and it may be a bit less cryptic than nls, i18n, or l10n. I was thinking intl, but your suggestion's better. Guys, you have been discussing the category *name* for eight days now without reaching a consensus. This is becoming somewhat boring. Please do not reinvent the wheel. Whether you like it or not, i18n is a well established and widely accepted acronym. -- 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: php5-readline-5.2.10 patch compile error
- Original Message - From: Andrea 'simplex' Zulato simp...@twopenguins.it To: freebsd-ports@freebsd.org Sent: Thursday, June 25, 2009 4:17 PM Subject: php5-readline-5.2.10 patch compile error Hi, i've upgraded php to 5.2.10 with portupgrade, php5-readline-5.2.10 won't compile. . . . 1 out of 3 hunks failed--saving rejects to config.m4.rej = Patch patch-config.m4 failed to apply cleanly. *** Error code 1 Same problem here. I´m using FreeBSD 6.4-STABLE ___ 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
