misconfigured package-build server causing bogus pkg-fallout messages
Immediately after Poudriere reports the OSVERSIONs: !!! Jail is newer than host. (Jail: 1100052, Host: 1100050) !!! !!! This is not supported. !!! !!! Host kernel must be same or newer than jail. !!! !!! Expect build failures. !!! Given that, I suppose the rest of the error report is bogus, right? Shouldn't stuff like this get filtered out, so that only genuine failures get sent to the maintainers? Message below, with emails altered to reduce spam. From: pkg-fallout [at] freebsd.org Date: Fri, 16 Jan 2015 06:45:55 GMT To: perryh [at] pluto.rain.com Subject: [package - head-amd64-default][sysutils/diskcheckd] Failed for diskcheckd-20110729 in build Cc: pkg-fallout [at] freebsd.org You are receiving this mail as a port that you maintain is failing to build on the FreeBSD package build server. Please investigate the failure and submit a PR to fix build. Maintainer: perryh [at] pluto.rain.com Last committer: vanilla [at] FreeBSD.org Ident: $FreeBSD: head/sysutils/diskcheckd/Makefile 359383 2014-06-26 16:00:00Z vanilla $ Log URL: http://beefy2.isc.freebsd.org/data/head-amd64-default/2015-01-15_15h59m45s/logs/diskcheckd-20110729.log Build URL: http://beefy2.isc.freebsd.org/build.html?mastername=head-amd64-default&build=2015-01-15_15h59m45s Log: >> Building sysutils/diskcheckd build started at Fri Jan 16 06:45:52 UTC 2015 port directory: /usr/ports/sysutils/diskcheckd building for: FreeBSD head-amd64-default-job-23 11.0-CURRENT FreeBSD 11.0-CURRENT r276772 amd64 maintained by: perryh [at] pluto.rain.com Makefile ident: $FreeBSD: head/sysutils/diskcheckd/Makefile 359383 2014-06-26 16:00:00Z vanilla $ Poudriere version: 3.1.1 Host OSVERSION: 1100050 Jail OSVERSION: 1100052 !!! Jail is newer than host. (Jail: 1100052, Host: 1100050) !!! !!! This is not supported. !!! !!! Host kernel must be same or newer than jail. !!! !!! Expect build failures. !!! ---Begin Environment--- OSVERSION=1100052 UNAME_v=FreeBSD 11.0-CURRENT r276772 UNAME_r=11.0-CURRENT BLOCKSIZE=K MAIL=/var/mail/root STATUS=1 SAVED_TERM= MASTERMNT=/usr/local/poudriere/data/.m/head-amd64-default/ref PATH=/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/root/bin POUDRIERE_BUILD_TYPE=bulk PKGNAME=diskcheckd-20110729 OLDPWD=/ PWD=/usr/local/poudriere/data/.m/head-amd64-default/ref/.p/pool MASTERNAME=head-amd64-default USER=root HOME=/root POUDRIERE_VERSION=3.1.1 LOCALBASE=/usr/local PACKAGE_BUILDING=yes ---End Environment--- ---Begin OPTIONS List--- ---End OPTIONS List--- --CONFIGURE_ARGS-- --End CONFIGURE_ARGS-- --CONFIGURE_ENV-- XDG_DATA_HOME=/wrkdirs/usr/ports/sysutils/diskcheckd/work XDG_CONFIG_HOME=/wrkdirs/usr/ports/sysutils/diskcheckd/work HOME=/wrkdirs/usr/ports/sysutils/diskcheckd/work TMPDIR="/tmp" SHELL=/bin/sh CONFIG_SHELL=/bin/sh --End CONFIGURE_ENV-- --MAKE_ENV-- XDG_DATA_HOME=/wrkdirs/usr/ports/sysutils/diskcheckd/work XDG_CONFIG_HOME=/wrkdirs/usr/ports/sysutils/diskcheckd/work HOME=/wrkdirs/usr/ports/sysutils/diskcheckd/work TMPDIR="/tmp" NO_PIE=yes SHELL=/bin/sh NO_LINT=YES PREFIX=/usr/local LOCALBASE=/usr/local LIBDIR="/usr/lib" CC="cc" CFLAGS="-O2 -pipe -D_PATH_CONF='\"/usr/local/etc/diskcheckd.conf\"' -fstack-protector -fno-strict-aliasing" CPP="cpp" CPPFLAGS="" LDFLAGS=" -fstack-protector" LIBS="" CXX="c++" CXXFLAGS="-O2 -pipe -D_PATH_CONF='\"/usr/local/etc/diskcheckd.conf\"' -fstack-protector -fno-strict-aliasing " MANPREFIX="/usr/local" BSD_INSTALL_PROGRAM="install -s -o root -g wheel -m 555" BSD_INSTALL_LIB="install -s -o root -g wheel -m 444" BSD_INSTALL_SCRIPT="install -o root -g wheel -m 555" BSD_INSTALL_DATA="install -o root -g wheel -m 0644" BSD_INSTALL_MAN="install -o root -g wheel -m 444" --End MAKE_ENV-- --PLIST_SUB-- OSREL=11.0 PREFIX=%D LOCALBASE=/usr/local RESETPREFIX=/usr/local PORTDOCS="" PORTEXAMPLES="" LIB32DIR=lib DOCSDIR="share/doc/diskcheckd" EXAMPLESDIR="share/examples/diskcheckd" DATADIR="share/diskcheckd" WWWDIR="www/diskcheckd" ETCDIR="etc/diskcheckd" --End PLIST_SUB-- --SUB_LIST-- PREFIX=/usr/local LOCALBASE=/usr/local DATADIR=/usr/local/share/diskcheckd DOCSDIR=/usr/local/share/doc/diskcheckd EXAMPLESDIR=/usr/local/share/examples/diskcheckd WWWDIR=/usr/local/www/diskcheckd ETCDIR=/usr/local/etc/diskcheckd --End SUB_LIST-- ---Begin make.conf--- USE_PACKAGE_DEPENDS=yes BATCH=yes WRKDIRPREFIX=/wrkdirs USE_PACKAGE_DEPENDS=yes BATCH=yes WRKDIRPREFIX=/wrkdirs PORTSDIR=/usr/ports PACKAGES=/packages DISTDIR=/distfiles /usr/local/etc/poudriere.d/make.conf WITH_PKGNG=yes #WITH_PKGNG=devel # clean-restricted ran via poudriere.conf NO_RESTRICTED #NO_RESTRICTED=yes DISABLE_MAKE_JOBS=poudriere ---End make.conf--- === ===> License BSD2CLAUSE accepted by the user === =
Re: CURRENT breaks loading of nvidia.so
Any hope to get a bit of text on this into the Handbook? Maybe with the example in Doug B.'s e-mail announcing it. (It's in the ports archive and DuckDuckGo can find it easily.) The example in build(7) is for a single module while Doug's message show that they should be space delimited. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com On Sat, Jan 17, 2015 at 9:28 PM, David Wolfskill wrote: > On Sat, Jan 17, 2015 at 09:22:06PM -0800, Kevin Oberman wrote: > > ... > > Can anyone tell me where PORTS_MODULES is documented? I don't find it in > > the Handbook. It's not in src.conf(5). I've known of it since Doug B. (I > > thing) wrote it. This is a very beneficial tool. It really needs to be > well > > documented. > > ... > > build(7) has it. > > (I confess that I didn't recall this, nor it it just "magically occur" > to me. Rather, brute force works again: > > grep -Zwr PORTS_MODULES /usr/share/man/man* > > Ugly, perhaps, but effective. :-}) > > Peace, > david > -- > David H. Wolfskill da...@catwhisker.org > Those who murder in the name of God or prophet are blasphemous cowards. > > See http://www.catwhisker.org/~david/publickey.gpg for my public key. > ___ 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: Problems with fusefs-ntfs port
from Stefan Ehmann: > After you get the "No such file or directory" error type > # dmesg | tail > Hopefully this will reveal a more helpful error message. Last message was a reference to "dhclient re0", which I did some time previous. > I'm currently not using fuse. But I think something like > # kldload fuse > might fix this issue. That did it! I couldn't find documentation on the need to "kldload fuse". I was then able to mount the NTFS drive (ntfs-3g) and rsync from it for backup. Tom ___ 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: CURRENT breaks loading of nvidia.so
On Sat, Jan 17, 2015 at 09:22:06PM -0800, Kevin Oberman wrote: > ... > Can anyone tell me where PORTS_MODULES is documented? I don't find it in > the Handbook. It's not in src.conf(5). I've known of it since Doug B. (I > thing) wrote it. This is a very beneficial tool. It really needs to be well > documented. > ... build(7) has it. (I confess that I didn't recall this, nor it it just "magically occur" to me. Rather, brute force works again: grep -Zwr PORTS_MODULES /usr/share/man/man* Ugly, perhaps, but effective. :-}) Peace, david -- David H. Wolfskill da...@catwhisker.org Those who murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgpPJ5CBkKiCM.pgp Description: PGP signature
Re: CURRENT breaks loading of nvidia.so
On Sat, Jan 17, 2015 at 8:34 PM, Bob Willcox wrote: > On Sat, Jan 17, 2015 at 07:48:37AM -0800, David Wolfskill wrote: > > On Sat, Jan 17, 2015 at 04:45:04PM +0100, Hans Petter Selasky wrote: > > > > > > Hi, > > > > > > The nvidia-driver package needs to be recompiled with the latest > > > FreeBSD-current sources, because of changes in the callout subsystem. > > > > > > If this is not possible, we can temporarily add the > "_callout_stop_safe" > > > symbol to the kernel for some transition time. > > > ... > > > > While I'm running i386 (vs. amd64), I have not encountered the cited > > issue. > > > > Given the above, I suspect that the fact that I have the line: > > > > PORTS_MODULES=x11/nvidia-driver > > > > > > in /etc/src.conf has a fair amount of (positive) influence on that. > > > > (I track stable/10 & head -- on different slices -- daily on my laptop.) > > > > Peace, > > david > > Thanks ALL! Adding the PORTS_MODULES=x11/nvidia-driver line to my > /etc/src.conf > file and rebuilding the kernel fixed it! > > Learn something new every day! :) > Can anyone tell me where PORTS_MODULES is documented? I don't find it in the Handbook. It's not in src.conf(5). I've known of it since Doug B. (I thing) wrote it. This is a very beneficial tool. It really needs to be well documented. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ 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: CURRENT breaks loading of nvidia.so
On Sat, Jan 17, 2015 at 07:48:37AM -0800, David Wolfskill wrote: > On Sat, Jan 17, 2015 at 04:45:04PM +0100, Hans Petter Selasky wrote: > > > > Hi, > > > > The nvidia-driver package needs to be recompiled with the latest > > FreeBSD-current sources, because of changes in the callout subsystem. > > > > If this is not possible, we can temporarily add the "_callout_stop_safe" > > symbol to the kernel for some transition time. > > ... > > While I'm running i386 (vs. amd64), I have not encountered the cited > issue. > > Given the above, I suspect that the fact that I have the line: > > PORTS_MODULES=x11/nvidia-driver > > > in /etc/src.conf has a fair amount of (positive) influence on that. > > (I track stable/10 & head -- on different slices -- daily on my laptop.) > > Peace, > david Thanks ALL! Adding the PORTS_MODULES=x11/nvidia-driver line to my /etc/src.conf file and rebuilding the kernel fixed it! Learn something new every day! :) Bob -- Bob Willcox| The Ancient Doctrine of Mind Over Matter: b...@immure.com | I don't mind... and you don't matter. Austin, TX | -- As revealed to reporter G. Rivera by Swami Havabanana ___ 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: CURRENT breaks loading of nvidia.so
On Sat, Jan 17, 2015 at 7:43 AM, Andreas Tobler wrote: > On 17.01.15 16:18, Bob Willcox wrote: > >> Yesterday when I upgraded my current box I encountered this failure when >> attempting to load the nvidia-driver (nvidia.so): >> >> link_elf_obj: symbol _callout_stop_safe undefined >> linker_load_file: Unsupported file type >> >> So, today I updtated my system again today hoping it might be fixed but >> the >> problem persists. >> >> System info: >> >> FreeBSD han.immure.com 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r277299: Sat >> Jan 17 08:52:41 CST 2015 b...@han.immure.com:/usr/obj/usr/src/sys/HAN >> amd64 >> > > I think you have to rebuild the nvidia-driver against your fresh built > system. At least I had and my T510 s working again with the nvidia.ko. > > David W. really has it right. If you rebuild the kernel, any port installing a kernel module needs to be rebuilt, as well. The use of PORT_MODULES in /etc/src.conf is the best way to make sure it happens. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkober...@gmail.com ___ 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: libfxp fails with poudriere but not as a port
On 01/15/15 20:35, Russell L. Carter wrote: Greetings, amd64 stable/10, updated across the failure. I've been watching a poudriere build failure with graphics/libfpx for several days now and investigated, and it is a curious failure. Some advice solicited on the fix. With an updated poudriere world, and an updated outside r277194 stable/10 world, graphics/libfxp fails with: I just settled down to work on this and I see that libfxp is now fixed and wdm and emacs-devel are alive again. I would love to learn what the problem was so that I can debug this sort of thing for myself quicker in the future. (pointer to relevant commit would be great!) Many thanks for the fix! Russell ___ 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: updating alpine port to new version (as a maintainer)
Good news - that means the port is now compiling fine, and the last thing you need to do is fix the pkg-plist file to ensure it accurately reflects all the files the port will install: # cd PORTDIR # make clean # make # make makeplist That will dump the new plist to the console standard output, but doesn't actually update the pkg-plist for you (you have to do that by redirecting the output to the file). But note, you need to follow the instructions of the first line (delete the first line, and check the output of the rest of the file looks reasonable). I would redirect the output to a new plist file and compare the difference before overwriting the main plist file: # make makeplist > pkg-plist.new # diff -u pkg-plist pkg-plist.new Then you can make the necessary changes to the pkg-plist file and delete the pkg-plist.new file. On Sunday, January 18, 2015, Marco Beishuizen wrote: > On Sat, 17 Jan 2015, the wise Scot Hetzel wrote: > > Well, problems with the maildir patch seem to have dissappeared, but I'm > not there yet. Alpine compiles, but the problems with the plist remain. > I'll look further into the Makefile and see if I can solve this. > > The current error is: > > > Compressing man pages (compress-man) > > Running Q/A tests (stage-qa) > > Checking for pkg-plist issues (check-plist) > ===> Parsing plist > ===> Checking for items in STAGEDIR missing from pkg-plist > Error: Orphaned: %%PORTDOCSDOCSDIR%%/tech-notes.txt > ===> Checking for items in pkg-plist which are not in STAGEDIR > Error: Missing: %%DOCSDIR%%/tech-notes/tech-notes.txt > ===> Error: Plist issues found. > *** Error code 1 > > Regards, > Marco > > -- -- From: Benjamin Woods woods...@gmail.com ___ 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: updating alpine port to new version (as a maintainer)
On Sat, 17 Jan 2015, the wise Scot Hetzel wrote: Well, problems with the maildir patch seem to have dissappeared, but I'm not there yet. Alpine compiles, but the problems with the plist remain. I'll look further into the Makefile and see if I can solve this. The current error is: > Compressing man pages (compress-man) > Running Q/A tests (stage-qa) > Checking for pkg-plist issues (check-plist) ===> Parsing plist ===> Checking for items in STAGEDIR missing from pkg-plist Error: Orphaned: %%PORTDOCSDOCSDIR%%/tech-notes.txt ===> Checking for items in pkg-plist which are not in STAGEDIR Error: Missing: %%DOCSDIR%%/tech-notes/tech-notes.txt ===> Error: Plist issues found. *** Error code 1 Regards, Marco -- I tell ya, drugs never worked out for me. The first time I tried smoking pot I didn't know what I was doing. I smoked half the joint, got the munchies, and ate the other half. Well, the first time I tried coke I was so embarrassed. I kept getting the bottle stuck up my nose. -- Rodney Dangerfield ___ 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: updating alpine port to new version (as a maintainer)
On Sat, 17 Jan 2015, the wise Scot Hetzel wrote:
Are you using the correct version of the maildir.patch.gz.
If you look on line 116 of the original Makefile, it shows:
116 PATCH_SITES= http://patches.freeiz.com/alpine/patches/alpine-2.11/
117 PATCHFILES+= maildir.patch.gz
You should change that line so that it shows alpine-2.20 or
alpine-${PORTVERSION} instead.
Yes I already saw this and changed it.
I checked the alpine-2.20/maildir.patch.gz and it shows that sm_read
requires 2 arguments.
Since the patch file isn't versioned, you will have to remove the file
from your distfiles and run make checksum to update the checksum for
the file.
This didn't work:
===> License APACHE20 accepted by the user
===> Found saved configuration for alpine-2.11_2
===> alpine-2.20 depends on file: /usr/local/sbin/pkg - found
=> alpine-2.20.tar.xz doesn't seem to exist in
/usr/ports/distfiles/alpine-2.20.
=> Attempting to fetch
http://patches.freeiz.com/alpine/release/src/alpine-2.20.tar.xz
alpine-2.20.tar.xz100% of 4717 kB 388 kBps
00m12s
=> maildir.patch.gz doesn't seem to exist in
/usr/ports/distfiles/alpine-2.20.
=> Attempting to fetch
http://patches.freeiz.com/alpine/patches/alpine-2.20/maildir.patch.gz
maildir.patch.gz 100% of 33 kB 5433 kBps
00m00s
===> Fetching all distfiles required by alpine-2.20 for building
=> SHA256 Checksum OK for alpine-2.20/alpine-2.20.tar.xz.
=> No SHA256 checksum recorded for alpine-2.20/maildir.patch.gz.
=> No suitable checksum found for alpine-2.20/maildir.patch.gz.
*** Error code 1
Another option is to change lines 116 and 117 to:
116 PATCH_SITES= http://patches.freeiz.com/alpine/patches/
117 PATCHFILES+= alpine-${PORTVERSION}/maildir.patch.gz
This will ensure everyone has the correct version of the maildir.patch.gz file.
Errors here too:
===> License APACHE20 accepted by the user
===> Found saved configuration for alpine-2.11_2
===> alpine-2.20 depends on file: /usr/local/sbin/pkg - found
===> Fetching all distfiles required by alpine-2.20 for building
=> SHA256 Checksum OK for alpine-2.20/alpine-2.20.tar.xz.
cannot open alpine-2.20/alpine-2.20/maildir.patch.gz: No such file or
directory
*** Error code 2
Regards,
Marco
--
I have made this letter longer than usual
because I lack the time to make it shorter.
-- Blaise Pascal
___
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: updating alpine port to new version (as a maintainer)
On Sat, Jan 17, 2015 at 2:54 PM, Marco Beishuizen wrote:
> On Sat, 17 Jan 2015, the wise Scot Hetzel wrote:
>
>> On line 41 of the current ports Makefile, it shows tech-notes.txt:
>>
>> 41 PORTDOCSdoc= brochure.txt tech-notes.txt
>>
>> Then on lines 163-164 in the post-install stage it tries to install them:
>>
>> 163 .for f in ${PORTDOCSdoc}
>> 164 ${INSTALL_MAN} ${WRKSRC}/doc/$f ${STAGEDIR}${DOCSDIR}
>> 165 .endfor
>>
>> Change the PORTDOCSdoc variable to:
>>
>> PORTDOCSdoc= brochure.txt tech-notes/tech-notes.txt
>>
>> This should install the tech-notes.txt file into the ${DOCSDIR}.
>>
>> The other option is to remove tech-notes.txt from PORTDOCSdoc and
>> added it to PORTDOCShtml. Then update the pkg-plist for the new
>> location.
>
>
> Thank you too Scot for your help. After adjusting these lines (and also one
> in line 145) this part seems to work.
>
> Now it gives a compile error and a lot of warnings during compiling.
>
> The 2 errors are:
>
> maildir.c:1720:66: error: too few arguments to function call, expected 2,
> have 1
> if (maildir_canonicalize (test, ref, pat) && (s = sm_read (&sdb))) {
> ~~~ ^
> maildir.c:1722:30: error: too few arguments to function call, expected 2,
> have 1
> while ((s = sm_read (&sdb)) != NULL); /* until no more subscriptions */
>
>
Are you using the correct version of the maildir.patch.gz.
If you look on line 116 of the original Makefile, it shows:
116 PATCH_SITES= http://patches.freeiz.com/alpine/patches/alpine-2.11/
117 PATCHFILES+= maildir.patch.gz
You should change that line so that it shows alpine-2.20 or
alpine-${PORTVERSION} instead.
I checked the alpine-2.20/maildir.patch.gz and it shows that sm_read
requires 2 arguments.
Since the patch file isn't versioned, you will have to remove the file
from your distfiles and run make checksum to update the checksum for
the file.
Another option is to change lines 116 and 117 to:
116 PATCH_SITES= http://patches.freeiz.com/alpine/patches/
117 PATCHFILES+= alpine-${PORTVERSION}/maildir.patch.gz
This will ensure everyone has the correct version of the maildir.patch.gz file.
--
DISCLAIMER:
No electrons were maimed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: updating alpine port to new version (as a maintainer)
On Sat, 17 Jan 2015, the wise Scot Hetzel wrote:
On line 41 of the current ports Makefile, it shows tech-notes.txt:
41 PORTDOCSdoc= brochure.txt tech-notes.txt
Then on lines 163-164 in the post-install stage it tries to install them:
163 .for f in ${PORTDOCSdoc}
164 ${INSTALL_MAN} ${WRKSRC}/doc/$f ${STAGEDIR}${DOCSDIR}
165 .endfor
Change the PORTDOCSdoc variable to:
PORTDOCSdoc= brochure.txt tech-notes/tech-notes.txt
This should install the tech-notes.txt file into the ${DOCSDIR}.
The other option is to remove tech-notes.txt from PORTDOCSdoc and
added it to PORTDOCShtml. Then update the pkg-plist for the new
location.
Thank you too Scot for your help. After adjusting these lines (and also
one in line 145) this part seems to work.
Now it gives a compile error and a lot of warnings during compiling.
The 2 errors are:
maildir.c:1720:66: error: too few arguments to function call, expected 2,
have 1
if (maildir_canonicalize (test, ref, pat) && (s = sm_read (&sdb))) {
~~~ ^
maildir.c:1722:30: error: too few arguments to function call, expected 2,
have 1
while ((s = sm_read (&sdb)) != NULL); /* until no more subscriptions
*/
Regards,
Marco
___
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: updating alpine port to new version (as a maintainer)
On Sat, Jan 17, 2015 at 1:48 PM, Marco Beishuizen wrote:
> On Sat, 17 Jan 2015, the wise Kurt Jaeger wrote:
>
>> I normally proceed by moving all non-applying patches into a seperate
>> directory and try if the build works:
>>
>> cd ~/myp/mail/alpine mkdir OLD mv files/patch-alpine__alpine.c OLD/
>>
>> # and retry rm -rf work && make check-plist
>>
>> If the patch is required (but different), one has to dig into the code and
>> find out what needs to change for the code to build.
>
>
> After removing 5 patches the make check-plist now hangs at:
>
> ===> License APACHE20 accepted by the user
> ===> Found saved configuration for alpine-2.11_2
> ===> alpine-2.20 depends on file: /usr/local/sbin/pkg - found
> ===> Fetching all distfiles required by alpine-2.20 for building
> ===> Extracting for alpine-2.20
> => SHA256 Checksum OK for alpine-2.20/alpine-2.20.tar.xz.
> => SHA256 Checksum OK for alpine-2.20/maildir.patch.gz.
> ===> Patching for alpine-2.20
> ===> Applying distribution patches for alpine-2.20
> ===> Applying FreeBSD patches for alpine-2.20
> cp: /home/marco/tmp/alpine/work/alpine-2.20/doc/tech-notes.txt: No such file
> or directory
> *** Error code 1
>
> The file tech-notes.txt is not in /doc/, but in /doc/tech-notes/. Where can
> I change this?
>
On line 41 of the current ports Makefile, it shows tech-notes.txt:
41 PORTDOCSdoc= brochure.txt tech-notes.txt
Then on lines 163-164 in the post-install stage it tries to install them:
163 .for f in ${PORTDOCSdoc}
164 ${INSTALL_MAN} ${WRKSRC}/doc/$f ${STAGEDIR}${DOCSDIR}
165 .endfor
Change the PORTDOCSdoc variable to:
PORTDOCSdoc= brochure.txt tech-notes/tech-notes.txt
This should install the tech-notes.txt file into the ${DOCSDIR}.
The other option is to remove tech-notes.txt from PORTDOCSdoc and
added it to PORTDOCShtml. Then update the pkg-plist for the new
location.
--
DISCLAIMER:
No electrons were maimed while sending this message. Only slightly bruised.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: updating alpine port to new version (as a maintainer)
On Sat, 17 Jan 2015, the wise Kurt Jaeger wrote: I normally proceed by moving all non-applying patches into a seperate directory and try if the build works: cd ~/myp/mail/alpine mkdir OLD mv files/patch-alpine__alpine.c OLD/ # and retry rm -rf work && make check-plist If the patch is required (but different), one has to dig into the code and find out what needs to change for the code to build. After removing 5 patches the make check-plist now hangs at: ===> License APACHE20 accepted by the user ===> Found saved configuration for alpine-2.11_2 ===> alpine-2.20 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by alpine-2.20 for building ===> Extracting for alpine-2.20 => SHA256 Checksum OK for alpine-2.20/alpine-2.20.tar.xz. => SHA256 Checksum OK for alpine-2.20/maildir.patch.gz. ===> Patching for alpine-2.20 ===> Applying distribution patches for alpine-2.20 ===> Applying FreeBSD patches for alpine-2.20 cp: /home/marco/tmp/alpine/work/alpine-2.20/doc/tech-notes.txt: No such file or directory *** Error code 1 The file tech-notes.txt is not in /doc/, but in /doc/tech-notes/. Where can I change this? Regards, Marco -- America, how can I write a holy litany in your silly mood? -- Allen Ginsberg ___ 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: updating alpine port to new version (as a maintainer)
Hi! > > # then I check the build and stuff on my test system (10.1-amd64) > > rm -rf work && make check-plist > > [ some iterations later ] > > When I do the make check-plist I get an error: > > ===> License APACHE20 accepted by the user > ===> Found saved configuration for alpine-2.11_2 > ===> alpine-2.20 depends on file: /usr/local/sbin/pkg - found > ===> Fetching all distfiles required by alpine-2.20 for building > ===> Extracting for alpine-2.20 > => SHA256 Checksum OK for alpine-2.20/alpine-2.20.tar.xz. > => SHA256 Checksum OK for alpine-2.20/maildir.patch.gz. > ===> Patching for alpine-2.20 > ===> Applying distribution patches for alpine-2.20 > ===> Applying FreeBSD patches for alpine-2.20 > Ignoring previously applied (or reversed) patch. > 2 out of 2 hunks ignored--saving rejects to ./alpine/alpine.c.rej > => Patch patch-alpine__alpine.c failed to apply cleanly. The patch files/patch-alpine__alpine.c no longer applies to the new version of the code. > Any ideas how to go from here? I normally proceed by moving all non-applying patches into a seperate directory and try if the build works: cd ~/myp/mail/alpine mkdir OLD mv files/patch-alpine__alpine.c OLD/ # and retry rm -rf work && make check-plist If the patch is required (but different), one has to dig into the code and find out what needs to change for the code to build. -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ 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: updating alpine port to new version (as a maintainer)
On Sat, 17 Jan 2015, the wise Kurt Jaeger wrote: Hi Kurt, Thanks for helping. Unfortunately not all things went as planned. # fix distinfo, make makesum does this for mw make makesum This looked fine. # then I check the build and stuff on my test system (10.1-amd64) rm -rf work && make check-plist [ some iterations later ] When I do the make check-plist I get an error: ===> License APACHE20 accepted by the user ===> Found saved configuration for alpine-2.11_2 ===> alpine-2.20 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by alpine-2.20 for building ===> Extracting for alpine-2.20 => SHA256 Checksum OK for alpine-2.20/alpine-2.20.tar.xz. => SHA256 Checksum OK for alpine-2.20/maildir.patch.gz. ===> Patching for alpine-2.20 ===> Applying distribution patches for alpine-2.20 ===> Applying FreeBSD patches for alpine-2.20 Ignoring previously applied (or reversed) patch. 2 out of 2 hunks ignored--saving rejects to ./alpine/alpine.c.rej => Patch patch-alpine__alpine.c failed to apply cleanly. => Patch(es) patch-alpine__Makefile.am patch-alpine__Makefile.in applied cleanly. *** Error code 1 The contents of alpine.c.rej are: @@ -50,7 +50,6 @@ #include "init.h" #include "remote.h" #include "pattern.h" -#include "newuser.h" #include "setup.h" #include "adrbkcmd.h" #include "signal.h" @@ -767,7 +766,6 @@ pine_state->mangled_header = 1; show_main_screen(pine_state, 0, FirstMenu, &main_keymenu, 0, (Pos *) NULL); - new_user_or_version(pine_state); ClearScreen(); } Any ideas how to go from here? Regards, Marco -- Woman would be more charming if one could fall into her arms without falling into her hands. -- DeGourmont ___ 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"
[no subject]
??? ___ 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"
pkg segmentation fault
This just happened today. Any comments/suggestions?
laptop_93: {356} # pkg -v
1.4.4
laptop_93: {357} # pkg delete p5-Archive-Zip
Checking integrity... done (0 conflicting)
Deinstallation has been requested for the following 1 packages (of 0
packages in the universe):
Installed packages to be REMOVED:
p5-Archive-Zip-1.42
The operation will free 226 kB.
Proceed with deinstalling packages? [y/N]: y
[1/1] Deinstalling p5-Archive-Zip-1.42...
[1/1] Deleting files for p5-Archive-Zip-1.42: 100%
laptop_93: {358} # pkg install p5-Archive-Zip
Updating FreeBSD repository catalogue...
FreeBSD repository is up-to-date.
All repositories are up-to-date.
apr-1.5.1.1.5.4 is locked and may not be modified
apr-1.5.1.1.5.4 is locked and may not be modified
apr-1.5.1.1.5.4 is locked and may not be modified
Checking integrity... done (0 conflicting)
The following 1 packages will be affected (of 0 checked):
New packages to be INSTALLED:
p5-Archive-Zip: 1.42
The process will require 226 kB more space.
Proceed with this action? [y/N]: y
[1/1] Installing p5-Archive-Zip-1.42...
[1/1] Extracting p5-Archive-Zip-1.42: 100%
Child process pid=50074 terminated abnormally: Segmentation fault: 11
--
Patrick Powell Astart Technologies
papow...@astart.com1530 Jamacha Rd, Suite X
Network and System San Diego, CA 92019
Consulting 858-874-6543 FAX 858-751-2435
Web: www.astart.com
___
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 build FireFox on 9.3/i386
On 01/17/15 17:19, Jan Beich wrote: Already reported. std::abs(int64_t) for 32bit archs or std::llabs are not available in base libstdc++ or before 10.0-RELEASE (r255294) for libstdc++ in lang/gcc47 and earlier (libstdc++/54686). https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196772 Thanks. Strangely, I had looked in the bug list, but didn't find this :-O In any case, it solved. bye av. ___ 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:PVC cards supplier
Dear Sir/Madam, A Smile day for you ! This is eva of a professional RFID card manufacturer from China . To welcome your Christmas Day,we prepare some presents for you,all of products are with an amazing discount ,some as follow for your reference: Mifare FM1108 1K (FUDAN) blank card-$ 0.093/pcs NXP Mifare 1k S50 blank card-$ 0.281/pcs NXP MIfare 4k S70 blank card-$ 0.529/pcs NFC NXP Ntag 213 blank card-$ 0.21/pcs NXP Desfire EV1 4K blank card-$ 0.909/pcs NXP PLUS S 2K blank card-$ 0.512/pcs Weclcome your more kind inquiry and questions . Very appreciate your soon reply . Thanks & Best Regards, eva Shenzhen Meihe Induction Technology Co., Ltd Tel:+86 755 2655 4636-803 Fax:+86 755 8602 1239 Cell:+86 13265758797 Skype:eva8901112 Web:www.mhgyjs.com www.mhrfid.com www.chinanfccard.com ___ 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: updating alpine port to new version (as a maintainer)
Hi!
> I am the port maintainer of the alpine port, nevertheless not a very
> experienced one.
>
> The alpine mailer has recently been updated from 2.11 to 2.20 and I as a
> maintainer would like to update the port to the new version.
>
> According to the porter's handbook I have to use diff to create a patch in
> order to upgrade the alpine port. Is this correct?
Yes.
Here's how I do updates:
I have
DEVELOPER=yes
in /etc/make.conf. I copy the current port to some temp directory:
cd /usr/ports && tar cf - mail/alpine | ( cd ~/myp; tar xf -)
Then I modify the copy:
cd ~/myp/mail/alpine
# change version
vi Makefile
# fix distinfo, make makesum does this for mw
make makesum
# then I check the build and stuff on my test system (10.1-amd64)
rm -rf work && make check-plist
[ some iterations later ]
# I then test it with poudriere in three architectures:
# copy to the poudriere ports tree (~/pp in my case):
cd ~/myp && tar cf - mail/alpine | ( cd ~/pp; tar xf -)
# and tests:
for i in 10x 93a 84i
do
name=`echo $port-$i | sed -e 's/\//__/g'`
echo -n "$i "
poudriere testport -j $i -o $port -n > ~/logs/${name}-${stmp}.txt
done
# if it works on all plattforms, I compare my changes to the old port:
cd /usr/ports && diff -r -u -N mail/alpine ~/myp/mail/alpine
This diff can be attached to the problem report in bugzilla.
--
p...@opsec.eu+49 171 3101372 5 years to go !
___
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"
updating alpine port to new version (as a maintainer)
Hi, I am the port maintainer of the alpine port, nevertheless not a very experienced one. The alpine mailer has recently been updated from 2.11 to 2.20 and I as a maintainer would like to update the port to the new version. According to the porter's handbook I have to use diff to create a patch in order to upgrade the alpine port. Is this correct? I'm hoping to get some pointers from an experienced port maintainer how to deal with upgrades like this. Thanks in advance for your help. Regards, Marco ___ 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 build FireFox on 9.3/i386
Andrea Venturoli writes:
> Due to the latest vulnerabilities, I'm trying to upgrade FireFox, but
> it stops on this error:
>
> In file included from
> /tmp/usr/ports/www/firefox/work/mozilla-release/obj-i386-portbld-freebsd9.3/content/media/Unified_cpp_content_media1.cpp:29:
> /tmp/usr/ports/www/firefox/work/mozilla-release/content/media/MediaDecoderStateMachine.cpp:1315:7:
> error: call to 'abs' is ambiguous
> std::abs(aDuration - duration) >
> ESTIMATED_DURATION_FUZZ_FACTOR_USECS) {
> ^~~~
> /usr/include/stdlib.h:83:6: note: candidate function
> int abs(int) __pure2;
> ^
> /usr/include/c++/4.2/cmath:89:3: note: candidate function
> abs(double __x)
> ^
> /usr/include/c++/4.2/cmath:93:3: note: candidate function
> abs(float __x)
> ^
> /usr/include/c++/4.2/cmath:97:3: note: candidate function
> abs(long double __x)
> ^
> /usr/include/c++/4.2/cstdlib:143:3: note: candidate function
> abs(long __i) { return labs(__i); }
> ^
> 1 error generated.
Already reported. std::abs(int64_t) for 32bit archs or std::llabs are not
available in base libstdc++ or before 10.0-RELEASE (r255294) for libstdc++
in lang/gcc47 and earlier (libstdc++/54686).
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196772
-
VFEmail.net - http://www.vfemail.net
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
___
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: CURRENT breaks loading of nvidia.so
On 17.01.15 16:18, Bob Willcox wrote: Yesterday when I upgraded my current box I encountered this failure when attempting to load the nvidia-driver (nvidia.so): link_elf_obj: symbol _callout_stop_safe undefined linker_load_file: Unsupported file type So, today I updtated my system again today hoping it might be fixed but the problem persists. System info: FreeBSD han.immure.com 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r277299: Sat Jan 17 08:52:41 CST 2015 b...@han.immure.com:/usr/obj/usr/src/sys/HAN amd64 I think you have to rebuild the nvidia-driver against your fresh built system. At least I had and my T510 s working again with the nvidia.ko. Gruss, Andreas ___ 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: CURRENT breaks loading of nvidia.so
On Sat, Jan 17, 2015 at 04:45:04PM +0100, Hans Petter Selasky wrote: > On 01/17/15 16:18, Bob Willcox wrote: > > Yesterday when I upgraded my current box I encountered this failure when > > attempting to load the nvidia-driver (nvidia.so): > > > > link_elf_obj: symbol _callout_stop_safe undefined > > linker_load_file: Unsupported file type > > > > So, today I updtated my system again today hoping it might be fixed but the > > problem persists. > > > > System info: > > > > FreeBSD han.immure.com 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r277299: Sat > > Jan 17 08:52:41 CST 2015 b...@han.immure.com:/usr/obj/usr/src/sys/HAN > > amd64 > > > > Thanks, > > Bob > > > > Hi, > > The nvidia-driver package needs to be recompiled with the latest > FreeBSD-current sources, because of changes in the callout subsystem. > > If this is not possible, we can temporarily add the "_callout_stop_safe" > symbol to the kernel for some transition time. > ... While I'm running i386 (vs. amd64), I have not encountered the cited issue. Given the above, I suspect that the fact that I have the line: PORTS_MODULES=x11/nvidia-driver in /etc/src.conf has a fair amount of (positive) influence on that. (I track stable/10 & head -- on different slices -- daily on my laptop.) Peace, david -- David H. Wolfskill da...@catwhisker.org Those who murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key. pgp1zSk8N1yXS.pgp Description: PGP signature
Re: CURRENT breaks loading of nvidia.so
On 01/17/15 16:18, Bob Willcox wrote: Yesterday when I upgraded my current box I encountered this failure when attempting to load the nvidia-driver (nvidia.so): link_elf_obj: symbol _callout_stop_safe undefined linker_load_file: Unsupported file type So, today I updtated my system again today hoping it might be fixed but the problem persists. System info: FreeBSD han.immure.com 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r277299: Sat Jan 17 08:52:41 CST 2015 b...@han.immure.com:/usr/obj/usr/src/sys/HAN amd64 Thanks, Bob Hi, The nvidia-driver package needs to be recompiled with the latest FreeBSD-current sources, because of changes in the callout subsystem. If this is not possible, we can temporarily add the "_callout_stop_safe" symbol to the kernel for some transition time. --HPS ___ 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"
CURRENT breaks loading of nvidia.so
Yesterday when I upgraded my current box I encountered this failure when attempting to load the nvidia-driver (nvidia.so): link_elf_obj: symbol _callout_stop_safe undefined linker_load_file: Unsupported file type So, today I updtated my system again today hoping it might be fixed but the problem persists. System info: FreeBSD han.immure.com 11.0-CURRENT FreeBSD 11.0-CURRENT #4 r277299: Sat Jan 17 08:52:41 CST 2015 b...@han.immure.com:/usr/obj/usr/src/sys/HAN amd64 Thanks, Bob -- Bob Willcox| The Ancient Doctrine of Mind Over Matter: b...@immure.com | I don't mind... and you don't matter. Austin, TX | -- As revealed to reporter G. Rivera by Swami Havabanana ___ 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: postgresql93 port and libedit
On Sat, Jan 17, 2015 at 7:00 AM, Waitman Gobble wrote:
> On Sat, Jan 17, 2015 at 6:54 AM, Baptiste Daroussin wrote:
>> On Sat, Jan 17, 2015 at 06:38:10AM -0800, Waitman Gobble wrote:
>>> On Sat, Jan 17, 2015 at 6:09 AM, Baptiste Daroussin
>>> wrote:
>>> > On Sat, Jan 17, 2015 at 10:37:49AM +0100, Palle Girgensohn wrote:
>>> >>
>>> >>
>>> >> 17 jan 2015 kl. 01:41 skrev Baptiste Daroussin :
>>> >>
>>> >> > On Thu, Jan 15, 2015 at 08:02:22PM -0800, Waitman Gobble wrote:
>>> >> >> On Thu, Jan 15, 2015 at 8:01 AM, Baptiste Daroussin
>>> >> >> wrote:
>>> >> >>> On Wed, Jan 14, 2015 at 10:27:14PM -0800, Waitman Gobble wrote:
>>> >> Hi,
>>> >>
>>> >> I noticed that postgresql93-client port pulls in readline, which is
>>> >> GPLv3.
>>> >> When I get rid of readline in Makefile 'USES' and also change the
>>> >> bottom of the Makefile in postgresql93-server,
>>> >>
>>> >> ...
>>> >> .include "${.CURDIR}/../postgresql92-server/Makefile"
>>> >>
>>> >> CONFIGURE_ARGS+=--with-libedit-preferred
>>> >>
>>> >>
>>> >> It builds without readline and links against libedit in base:
>>> >>
>>> >> >>> except that libedit is not really an alternative as it does not
>>> >> >>> supprot unicode
>>> >> >>> (except in head) one solution would be to try linking against the
>>> >> >>> editline port
>>> >> >>> which contains the same fixes as libedit in head and see if it works.
>>> >> >>>
>>> >> >>> Best regards,
>>> >> >>> Bapt
>>> >> >>
>>> >> >> Thanks so much for the feedback. I've considered the options regarding
>>> >> >> my project and I think it's more work to handle end-user devices with
>>> >> >> a pkg repository if I indeed must manage custom ports built using
>>> >> >> customized sources. Distributing the initial appliance isn't the
>>> >> >> problem, i'm working out an update strategy for down the road.
>>> >> >>
>>> >> >
>>> >> > https://people.freebsd.org/~bapt/pglibedit.diff
>>> >> >
>>> >> > This patch works for me and accepts perfectly unicode.
>>> >> >
>>> >> > Can anyone from the postgresql team test, generalize to other
>>> >> > postegresql
>>> >> > versions? (please keep it using the port version of libedit).
>>> >> >
>>> >> > Best regards,
>>> >> > Bapt
>>> >>
>>> >> Hi,
>>> >>
>>> >> Looks like a reasonable patch. I have a hard time finding the
>>> >> differences between readine and ilbedit. It aims at 100% API
>>> >> compatibility. How good is libedit? If it degrades functionality
>>> >> compared to readline it should really be an option, but I agree, lesser
>>> >> options are preferred.
>>> >>
>>> >> Palle
>>> > It is not 100% compatible but I think it implements all pgsql
>>> > requirements, only
>>> > the version in ports and he head handle correctly unicode.
>>> >
>>> > Some of the default settings are a bit different most ^W but that can be
>>> > changed
>>> > via .editrc
>>> >
>>> > mysql has tips about the differences:
>>> > https://docs.oracle.com/cd/E17952_01/refman-5.6-en/mysql-tips.html
>>> >
>>> > From what I can read in the code psql only uses compatible interfaces.
>>> >
>>> > As the one who have done the latet updates on libedit both base and
>>> > ports, I
>>> > would recommand to only use the version from ports on all version of
>>> > FreeBSD as
>>> > I can add quick fixes if needed.
>>> >
>>> > Once I'm sure the libedit in base is good enough everywhere we would be
>>> > able to
>>> > switch on the base version if people prefers to avoid an external dep.
>>> >
>>> > Best regards,
>>> > Bapt
>>>
>>> Looks great. The patch looks fine, however there is an issue that the
>>> configure script in postgresql93 src still needs readline. If readline
>>> is already on the machine then it builds fine, however if it is not
>>> then the build fails. adding 'readline' back into USES will fix that
>>> problem, and the resulting client is still linked to libedit and not
>>> readline.. however the pkg will show a dependency on readline and pull
>>> that in. The configure script is based on having readline, if you use
>>> the --without-readline switch it won't even use libedit, however if
>>> you use --with-libedit-preferred it will check for readline and then
>>> switch the library linking order from 'readline libedit' to 'libedit
>>> readline'.
>>>
>>> I think the configure script for postgresql needs some rework so that
>>> it only uses libedit, and the option would be --with-readline or
>>> --with-libedit.
>>>
>>> if 'readline' is removed from the Makefile (and readline is already
>>> installed on the machine) then the package will build fine without the
>>> dependency on readline. It's kind of a tricky predicament that it
>>> needs it but not really.
>>>
>>> As far as a port, I'm not sure how to 'optionally' replace the
>>> configure script with what is in 'files' if the libedit option is
>>> selected. I'm sure there is an example in the ports tree, just haven't
>>> yet taken the time to check.
>>>
>>
>> I have no r
Re: postgresql93 port and libedit
On Sat, Jan 17, 2015 at 6:54 AM, Baptiste Daroussin wrote:
> On Sat, Jan 17, 2015 at 06:38:10AM -0800, Waitman Gobble wrote:
>> On Sat, Jan 17, 2015 at 6:09 AM, Baptiste Daroussin wrote:
>> > On Sat, Jan 17, 2015 at 10:37:49AM +0100, Palle Girgensohn wrote:
>> >>
>> >>
>> >> 17 jan 2015 kl. 01:41 skrev Baptiste Daroussin :
>> >>
>> >> > On Thu, Jan 15, 2015 at 08:02:22PM -0800, Waitman Gobble wrote:
>> >> >> On Thu, Jan 15, 2015 at 8:01 AM, Baptiste Daroussin
>> >> >> wrote:
>> >> >>> On Wed, Jan 14, 2015 at 10:27:14PM -0800, Waitman Gobble wrote:
>> >> Hi,
>> >>
>> >> I noticed that postgresql93-client port pulls in readline, which is
>> >> GPLv3.
>> >> When I get rid of readline in Makefile 'USES' and also change the
>> >> bottom of the Makefile in postgresql93-server,
>> >>
>> >> ...
>> >> .include "${.CURDIR}/../postgresql92-server/Makefile"
>> >>
>> >> CONFIGURE_ARGS+=--with-libedit-preferred
>> >>
>> >>
>> >> It builds without readline and links against libedit in base:
>> >>
>> >> >>> except that libedit is not really an alternative as it does not
>> >> >>> supprot unicode
>> >> >>> (except in head) one solution would be to try linking against the
>> >> >>> editline port
>> >> >>> which contains the same fixes as libedit in head and see if it works.
>> >> >>>
>> >> >>> Best regards,
>> >> >>> Bapt
>> >> >>
>> >> >> Thanks so much for the feedback. I've considered the options regarding
>> >> >> my project and I think it's more work to handle end-user devices with
>> >> >> a pkg repository if I indeed must manage custom ports built using
>> >> >> customized sources. Distributing the initial appliance isn't the
>> >> >> problem, i'm working out an update strategy for down the road.
>> >> >>
>> >> >
>> >> > https://people.freebsd.org/~bapt/pglibedit.diff
>> >> >
>> >> > This patch works for me and accepts perfectly unicode.
>> >> >
>> >> > Can anyone from the postgresql team test, generalize to other
>> >> > postegresql
>> >> > versions? (please keep it using the port version of libedit).
>> >> >
>> >> > Best regards,
>> >> > Bapt
>> >>
>> >> Hi,
>> >>
>> >> Looks like a reasonable patch. I have a hard time finding the differences
>> >> between readine and ilbedit. It aims at 100% API compatibility. How good
>> >> is libedit? If it degrades functionality compared to readline it should
>> >> really be an option, but I agree, lesser options are preferred.
>> >>
>> >> Palle
>> > It is not 100% compatible but I think it implements all pgsql
>> > requirements, only
>> > the version in ports and he head handle correctly unicode.
>> >
>> > Some of the default settings are a bit different most ^W but that can be
>> > changed
>> > via .editrc
>> >
>> > mysql has tips about the differences:
>> > https://docs.oracle.com/cd/E17952_01/refman-5.6-en/mysql-tips.html
>> >
>> > From what I can read in the code psql only uses compatible interfaces.
>> >
>> > As the one who have done the latet updates on libedit both base and ports,
>> > I
>> > would recommand to only use the version from ports on all version of
>> > FreeBSD as
>> > I can add quick fixes if needed.
>> >
>> > Once I'm sure the libedit in base is good enough everywhere we would be
>> > able to
>> > switch on the base version if people prefers to avoid an external dep.
>> >
>> > Best regards,
>> > Bapt
>>
>> Looks great. The patch looks fine, however there is an issue that the
>> configure script in postgresql93 src still needs readline. If readline
>> is already on the machine then it builds fine, however if it is not
>> then the build fails. adding 'readline' back into USES will fix that
>> problem, and the resulting client is still linked to libedit and not
>> readline.. however the pkg will show a dependency on readline and pull
>> that in. The configure script is based on having readline, if you use
>> the --without-readline switch it won't even use libedit, however if
>> you use --with-libedit-preferred it will check for readline and then
>> switch the library linking order from 'readline libedit' to 'libedit
>> readline'.
>>
>> I think the configure script for postgresql needs some rework so that
>> it only uses libedit, and the option would be --with-readline or
>> --with-libedit.
>>
>> if 'readline' is removed from the Makefile (and readline is already
>> installed on the machine) then the package will build fine without the
>> dependency on readline. It's kind of a tricky predicament that it
>> needs it but not really.
>>
>> As far as a port, I'm not sure how to 'optionally' replace the
>> configure script with what is in 'files' if the libedit option is
>> selected. I'm sure there is an example in the ports tree, just haven't
>> yet taken the time to check.
>>
>
> I have no readline installed and I can see:
> checking for rl_completion_append_character... no
> checking for rl_completion_matches... yes
> checking for rl_filename_completion_function... yes
> c
Re: postgresql93 port and libedit
On Sat, Jan 17, 2015 at 06:38:10AM -0800, Waitman Gobble wrote:
> On Sat, Jan 17, 2015 at 6:09 AM, Baptiste Daroussin wrote:
> > On Sat, Jan 17, 2015 at 10:37:49AM +0100, Palle Girgensohn wrote:
> >>
> >>
> >> 17 jan 2015 kl. 01:41 skrev Baptiste Daroussin :
> >>
> >> > On Thu, Jan 15, 2015 at 08:02:22PM -0800, Waitman Gobble wrote:
> >> >> On Thu, Jan 15, 2015 at 8:01 AM, Baptiste Daroussin
> >> >> wrote:
> >> >>> On Wed, Jan 14, 2015 at 10:27:14PM -0800, Waitman Gobble wrote:
> >> Hi,
> >>
> >> I noticed that postgresql93-client port pulls in readline, which is
> >> GPLv3.
> >> When I get rid of readline in Makefile 'USES' and also change the
> >> bottom of the Makefile in postgresql93-server,
> >>
> >> ...
> >> .include "${.CURDIR}/../postgresql92-server/Makefile"
> >>
> >> CONFIGURE_ARGS+=--with-libedit-preferred
> >>
> >>
> >> It builds without readline and links against libedit in base:
> >>
> >> >>> except that libedit is not really an alternative as it does not
> >> >>> supprot unicode
> >> >>> (except in head) one solution would be to try linking against the
> >> >>> editline port
> >> >>> which contains the same fixes as libedit in head and see if it works.
> >> >>>
> >> >>> Best regards,
> >> >>> Bapt
> >> >>
> >> >> Thanks so much for the feedback. I've considered the options regarding
> >> >> my project and I think it's more work to handle end-user devices with
> >> >> a pkg repository if I indeed must manage custom ports built using
> >> >> customized sources. Distributing the initial appliance isn't the
> >> >> problem, i'm working out an update strategy for down the road.
> >> >>
> >> >
> >> > https://people.freebsd.org/~bapt/pglibedit.diff
> >> >
> >> > This patch works for me and accepts perfectly unicode.
> >> >
> >> > Can anyone from the postgresql team test, generalize to other postegresql
> >> > versions? (please keep it using the port version of libedit).
> >> >
> >> > Best regards,
> >> > Bapt
> >>
> >> Hi,
> >>
> >> Looks like a reasonable patch. I have a hard time finding the differences
> >> between readine and ilbedit. It aims at 100% API compatibility. How good
> >> is libedit? If it degrades functionality compared to readline it should
> >> really be an option, but I agree, lesser options are preferred.
> >>
> >> Palle
> > It is not 100% compatible but I think it implements all pgsql requirements,
> > only
> > the version in ports and he head handle correctly unicode.
> >
> > Some of the default settings are a bit different most ^W but that can be
> > changed
> > via .editrc
> >
> > mysql has tips about the differences:
> > https://docs.oracle.com/cd/E17952_01/refman-5.6-en/mysql-tips.html
> >
> > From what I can read in the code psql only uses compatible interfaces.
> >
> > As the one who have done the latet updates on libedit both base and ports, I
> > would recommand to only use the version from ports on all version of
> > FreeBSD as
> > I can add quick fixes if needed.
> >
> > Once I'm sure the libedit in base is good enough everywhere we would be
> > able to
> > switch on the base version if people prefers to avoid an external dep.
> >
> > Best regards,
> > Bapt
>
> Looks great. The patch looks fine, however there is an issue that the
> configure script in postgresql93 src still needs readline. If readline
> is already on the machine then it builds fine, however if it is not
> then the build fails. adding 'readline' back into USES will fix that
> problem, and the resulting client is still linked to libedit and not
> readline.. however the pkg will show a dependency on readline and pull
> that in. The configure script is based on having readline, if you use
> the --without-readline switch it won't even use libedit, however if
> you use --with-libedit-preferred it will check for readline and then
> switch the library linking order from 'readline libedit' to 'libedit
> readline'.
>
> I think the configure script for postgresql needs some rework so that
> it only uses libedit, and the option would be --with-readline or
> --with-libedit.
>
> if 'readline' is removed from the Makefile (and readline is already
> installed on the machine) then the package will build fine without the
> dependency on readline. It's kind of a tricky predicament that it
> needs it but not really.
>
> As far as a port, I'm not sure how to 'optionally' replace the
> configure script with what is in 'files' if the libedit option is
> selected. I'm sure there is an example in the ports tree, just haven't
> yet taken the time to check.
>
I have no readline installed and I can see:
checking for rl_completion_append_character... no
checking for rl_completion_matches... yes
checking for rl_filename_completion_function... yes
checking for append_history... no
checking for history_truncate_file... yes
Which is what I was expected.
With libedit-prefered it checks:
READLINE_ORDER="-ledit -lreadline"
So from what I ca
Cannot build FireFox on 9.3/i386
Hello.
Due to the latest vulnerabilities, I'm trying to upgrade FireFox, but it
stops on this error:
clang++ -o Unified_cpp_content_media2.o -c -I../../dist/stl_wrappers
-I../../dist/system_wrappers -include
/tmp/usr/ports/www/firefox/work/mozilla-release/config/gcc_hidden.h
-DOS_POSIX=1 -DOS_FREEBSD=1 -DOS_BSD=1 -DMOZILLA_INTERNAL_API
-DSTATIC_EXPORTABLE_JS_API -DMOZILLA_INTERNAL_API -DIMPL_LIBXUL
-DMOZ_GLUE_IN_PROGRAM -DAB_CD=en-US -DNO_NSPR_10_SUPPORT
-I/tmp/usr/ports/www/firefox/work/mozilla-release/content/media -I.
-I/tmp/usr/ports/www/firefox/work/mozilla-release/obj-i386-portbld-freebsd9.3/ipc/ipdl/_ipdlheaders
-I/tmp/usr/ports/www/firefox/work/mozilla-release/ipc/chromium/src
-I/tmp/usr/ports/www/firefox/work/mozilla-release/ipc/glue
-I/tmp/usr/ports/www/firefox/work/mozilla-release/content/base/src
-I/tmp/usr/ports/www/firefox/work/mozilla-release/layout/generic
-I/tmp/usr/ports/www/firefox/work/mozilla-release/layout/xul
-I/tmp/usr/ports/www/firefox/work/mozilla-release/netwerk/base/src
-I../../dist/include -I/usr/local/include/nspr
-I/usr/local/include/nss -I/usr/local/include/nss/nss
-I/usr/local/include -I/usr/local/include -I/usr/local/include/pixman-1
-fPIC -Qunused-arguments -isystem/usr/local/include
-I/usr/local/include -DMOZILLA_CLIENT -include ../../mozilla-config.h
-MD -MP -MF .deps/Unified_cpp_content_media2.o.pp -Qunused-arguments
-isystem/usr/local/include -I/usr/local/include -Qunused-arguments
-Wall -Wempty-body -Woverloaded-virtual -Wsign-compare -Wwrite-strings
-Werror=endif-labels -Werror=int-to-pointer-cast -Werror=missing-braces
-Werror=pointer-arith -Werror=return-type -Werror=sequence-point
-Werror=unused-label -Werror=trigraphs -Werror=type-limits
-Wno-invalid-offsetof -Wno-inline-new-delete -Wno-c++0x-extensions
-Wno-extended-offsetof -Wno-unknown-warning-option
-Wno-return-type-c-linkage -O2 -pipe -fno-strict-aliasing
-fno-exceptions -fno-strict-aliasing -fno-rtti -ffunction-sections
-fdata-sections -fno-exceptions -fno-math-errno -std=gnu++0x -pipe
-DNDEBUG -DTRIMMED -fno-omit-frame-pointer -I/usr/local/include
-I/usr/local/include -I/usr/local/include/opus
-I/usr/local/include/soundtouch
/tmp/usr/ports/www/firefox/work/mozilla-release/obj-i386-portbld-freebsd9.3/content/media/Unified_cpp_content_media2.cpp
In file included from
/tmp/usr/ports/www/firefox/work/mozilla-release/obj-i386-portbld-freebsd9.3/content/media/Unified_cpp_content_media1.cpp:29:
/tmp/usr/ports/www/firefox/work/mozilla-release/content/media/MediaDecoderStateMachine.cpp:1315:7:
error: call to 'abs' is ambiguous
std::abs(aDuration - duration) >
ESTIMATED_DURATION_FUZZ_FACTOR_USECS) {
^~~~
/usr/include/stdlib.h:83:6: note: candidate function
int abs(int) __pure2;
^
/usr/include/c++/4.2/cmath:89:3: note: candidate function
abs(double __x)
^
/usr/include/c++/4.2/cmath:93:3: note: candidate function
abs(float __x)
^
/usr/include/c++/4.2/cmath:97:3: note: candidate function
abs(long double __x)
^
/usr/include/c++/4.2/cstdlib:143:3: note: candidate function
abs(long __i) { return labs(__i); }
^
1 error generated.
/tmp/usr/ports/www/firefox/work/mozilla-release/config/rules.mk:948:
recipe for target 'Unified_cpp_content_media1.o' failed
Any hint?
Is firefox 35 still supported on 9.3 or should I move to ESR?
bye & Thanks
av.
___
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: postgresql93 port and libedit
On Sat, Jan 17, 2015 at 6:09 AM, Baptiste Daroussin wrote:
> On Sat, Jan 17, 2015 at 10:37:49AM +0100, Palle Girgensohn wrote:
>>
>>
>> 17 jan 2015 kl. 01:41 skrev Baptiste Daroussin :
>>
>> > On Thu, Jan 15, 2015 at 08:02:22PM -0800, Waitman Gobble wrote:
>> >> On Thu, Jan 15, 2015 at 8:01 AM, Baptiste Daroussin
>> >> wrote:
>> >>> On Wed, Jan 14, 2015 at 10:27:14PM -0800, Waitman Gobble wrote:
>> Hi,
>>
>> I noticed that postgresql93-client port pulls in readline, which is
>> GPLv3.
>> When I get rid of readline in Makefile 'USES' and also change the
>> bottom of the Makefile in postgresql93-server,
>>
>> ...
>> .include "${.CURDIR}/../postgresql92-server/Makefile"
>>
>> CONFIGURE_ARGS+=--with-libedit-preferred
>>
>>
>> It builds without readline and links against libedit in base:
>>
>> >>> except that libedit is not really an alternative as it does not supprot
>> >>> unicode
>> >>> (except in head) one solution would be to try linking against the
>> >>> editline port
>> >>> which contains the same fixes as libedit in head and see if it works.
>> >>>
>> >>> Best regards,
>> >>> Bapt
>> >>
>> >> Thanks so much for the feedback. I've considered the options regarding
>> >> my project and I think it's more work to handle end-user devices with
>> >> a pkg repository if I indeed must manage custom ports built using
>> >> customized sources. Distributing the initial appliance isn't the
>> >> problem, i'm working out an update strategy for down the road.
>> >>
>> >
>> > https://people.freebsd.org/~bapt/pglibedit.diff
>> >
>> > This patch works for me and accepts perfectly unicode.
>> >
>> > Can anyone from the postgresql team test, generalize to other postegresql
>> > versions? (please keep it using the port version of libedit).
>> >
>> > Best regards,
>> > Bapt
>>
>> Hi,
>>
>> Looks like a reasonable patch. I have a hard time finding the differences
>> between readine and ilbedit. It aims at 100% API compatibility. How good is
>> libedit? If it degrades functionality compared to readline it should really
>> be an option, but I agree, lesser options are preferred.
>>
>> Palle
> It is not 100% compatible but I think it implements all pgsql requirements,
> only
> the version in ports and he head handle correctly unicode.
>
> Some of the default settings are a bit different most ^W but that can be
> changed
> via .editrc
>
> mysql has tips about the differences:
> https://docs.oracle.com/cd/E17952_01/refman-5.6-en/mysql-tips.html
>
> From what I can read in the code psql only uses compatible interfaces.
>
> As the one who have done the latet updates on libedit both base and ports, I
> would recommand to only use the version from ports on all version of FreeBSD
> as
> I can add quick fixes if needed.
>
> Once I'm sure the libedit in base is good enough everywhere we would be able
> to
> switch on the base version if people prefers to avoid an external dep.
>
> Best regards,
> Bapt
Looks great. The patch looks fine, however there is an issue that the
configure script in postgresql93 src still needs readline. If readline
is already on the machine then it builds fine, however if it is not
then the build fails. adding 'readline' back into USES will fix that
problem, and the resulting client is still linked to libedit and not
readline.. however the pkg will show a dependency on readline and pull
that in. The configure script is based on having readline, if you use
the --without-readline switch it won't even use libedit, however if
you use --with-libedit-preferred it will check for readline and then
switch the library linking order from 'readline libedit' to 'libedit
readline'.
I think the configure script for postgresql needs some rework so that
it only uses libedit, and the option would be --with-readline or
--with-libedit.
if 'readline' is removed from the Makefile (and readline is already
installed on the machine) then the package will build fine without the
dependency on readline. It's kind of a tricky predicament that it
needs it but not really.
As far as a port, I'm not sure how to 'optionally' replace the
configure script with what is in 'files' if the libedit option is
selected. I'm sure there is an example in the ports tree, just haven't
yet taken the time to check.
--
Waitman Gobble
Los Altos California USA
510-830-7975
___
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: postgresql93 port and libedit
On Sat, Jan 17, 2015 at 10:37:49AM +0100, Palle Girgensohn wrote:
>
>
> 17 jan 2015 kl. 01:41 skrev Baptiste Daroussin :
>
> > On Thu, Jan 15, 2015 at 08:02:22PM -0800, Waitman Gobble wrote:
> >> On Thu, Jan 15, 2015 at 8:01 AM, Baptiste Daroussin
> >> wrote:
> >>> On Wed, Jan 14, 2015 at 10:27:14PM -0800, Waitman Gobble wrote:
> Hi,
>
> I noticed that postgresql93-client port pulls in readline, which is
> GPLv3.
> When I get rid of readline in Makefile 'USES' and also change the
> bottom of the Makefile in postgresql93-server,
>
> ...
> .include "${.CURDIR}/../postgresql92-server/Makefile"
>
> CONFIGURE_ARGS+=--with-libedit-preferred
>
>
> It builds without readline and links against libedit in base:
>
> >>> except that libedit is not really an alternative as it does not supprot
> >>> unicode
> >>> (except in head) one solution would be to try linking against the
> >>> editline port
> >>> which contains the same fixes as libedit in head and see if it works.
> >>>
> >>> Best regards,
> >>> Bapt
> >>
> >> Thanks so much for the feedback. I've considered the options regarding
> >> my project and I think it's more work to handle end-user devices with
> >> a pkg repository if I indeed must manage custom ports built using
> >> customized sources. Distributing the initial appliance isn't the
> >> problem, i'm working out an update strategy for down the road.
> >>
> >
> > https://people.freebsd.org/~bapt/pglibedit.diff
> >
> > This patch works for me and accepts perfectly unicode.
> >
> > Can anyone from the postgresql team test, generalize to other postegresql
> > versions? (please keep it using the port version of libedit).
> >
> > Best regards,
> > Bapt
>
> Hi,
>
> Looks like a reasonable patch. I have a hard time finding the differences
> between readine and ilbedit. It aims at 100% API compatibility. How good is
> libedit? If it degrades functionality compared to readline it should really
> be an option, but I agree, lesser options are preferred.
>
> Palle
It is not 100% compatible but I think it implements all pgsql requirements, only
the version in ports and he head handle correctly unicode.
Some of the default settings are a bit different most ^W but that can be changed
via .editrc
mysql has tips about the differences:
https://docs.oracle.com/cd/E17952_01/refman-5.6-en/mysql-tips.html
From what I can read in the code psql only uses compatible interfaces.
As the one who have done the latet updates on libedit both base and ports, I
would recommand to only use the version from ports on all version of FreeBSD as
I can add quick fixes if needed.
Once I'm sure the libedit in base is good enough everywhere we would be able to
switch on the base version if people prefers to avoid an external dep.
Best regards,
Bapt
pgpkY8yPqnAmF.pgp
Description: PGP signature
Re: postgresql93 port and libedit
17 jan 2015 kl. 01:41 skrev Baptiste Daroussin :
> On Thu, Jan 15, 2015 at 08:02:22PM -0800, Waitman Gobble wrote:
>> On Thu, Jan 15, 2015 at 8:01 AM, Baptiste Daroussin wrote:
>>> On Wed, Jan 14, 2015 at 10:27:14PM -0800, Waitman Gobble wrote:
Hi,
I noticed that postgresql93-client port pulls in readline, which is GPLv3.
When I get rid of readline in Makefile 'USES' and also change the
bottom of the Makefile in postgresql93-server,
...
.include "${.CURDIR}/../postgresql92-server/Makefile"
CONFIGURE_ARGS+=--with-libedit-preferred
It builds without readline and links against libedit in base:
>>> except that libedit is not really an alternative as it does not supprot
>>> unicode
>>> (except in head) one solution would be to try linking against the editline
>>> port
>>> which contains the same fixes as libedit in head and see if it works.
>>>
>>> Best regards,
>>> Bapt
>>
>> Thanks so much for the feedback. I've considered the options regarding
>> my project and I think it's more work to handle end-user devices with
>> a pkg repository if I indeed must manage custom ports built using
>> customized sources. Distributing the initial appliance isn't the
>> problem, i'm working out an update strategy for down the road.
>>
>
> https://people.freebsd.org/~bapt/pglibedit.diff
>
> This patch works for me and accepts perfectly unicode.
>
> Can anyone from the postgresql team test, generalize to other postegresql
> versions? (please keep it using the port version of libedit).
>
> Best regards,
> Bapt
Hi,
Looks like a reasonable patch. I have a hard time finding the differences
between readine and ilbedit. It aims at 100% API compatibility. How good is
libedit? If it degrades functionality compared to readline it should really be
an option, but I agree, lesser options are preferred.
Palle
___
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"
