Re: TEX_DEFAULT problem
Hi, Please resolve %%TEXMFDIR%% of devel/tex-kpathsea/pkg-plist that could be once unfolded with definition at Mk/bsd.tex.mk which you unloaded. I have no idea where TEXMFDIR?="share/texmf" should be suggested and processed in the PLIST_SUB variable list when USE_TEX macro is unavailable. 2013/5/10, Hiroki Sato : > ...snip... > I already fixed this in r317773. ___ 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"
Shilpa's Invite to Goa for freebsd-ports@freebsd.org
- This mail is a HTML mail. Not all elements could be shown in plain text mode. - Hi, A trip to Goa is a very memorable one as Goa is a lovely place of visit. And to make that trip even more memorable, one needs to plan the trip very smartly. There are several guidelines which are to be followed while planning a trip to Goa. We have the ultimate guide for your trip in goa. Visit us at: http://mtsdatacard.asia Thanks for your valubale time Regards ... Shilpa Gosai ___ 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: ports/119546
On 05/10/13 15:50, b.f. wrote:
I don't think so, other than the ports Makefiles. With regard to
bsd.openssl.mk, I was referring to:
59 .if defined(WITH_OPENSSL_BASE)
,,,
73 .if exists(${LOCALBASE}/lib/libcrypto.so)
74 check-depends::
75 @${ECHO_CMD} "Dependency error: this port wants the
OpenSSL library from the FreeBSD"
76 @${ECHO_CMD} "base system. You can't build against it,
while a newer"
77 @${ECHO_CMD} "version is installed by a port."
78 @${ECHO_CMD} "Please deinstall the port or undefine
WITH_OPENSSL_BASE."
79 @${FALSE}
80 .endif
Thanks a lot; now I've got a clear picture.
You can try to work around the problem by not using USE_OPENSSL, but
instead adding the openssl dependencies, link line and rpath
additions, etc. in the port Makefile. A number of ports used to do
this, for various reasons. However, this should only be done when
necessary, to prevent the proliferation of ad hoc methods of using
openssl in the ports tree, which makes maintenance more difficult.
Here's what I did:
# find /usr/ports -type f -exec grep -l OPENSS_PORT "{}" ";"
This showed very few ports really requiring openssl from ports, none of
which I had currently installed.
So I moved its libraries to /usr/local/lib/compat/pkg/ and pkg_deleted
(-f) it. Newer compilations would pick up base, then.
A "portupgrade -Rf nss_ldap" later, I can once more use ssh.
ThunderBird still does not start, but I'll investigate later.
A real solution (probably as good a solution as we can arrive at
without investing a lot more time in patching many different ports, or
fundamentally changing the way that we handle linking) would be to
change the openssl port and bsd.openssl,mk to install the
security/openssl libraries in a location other than ${LOCALBASE}/lib
I'm no expert, but I would vote for a solution to be found and this one
seems good to me.
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"
security/libgcrypt checksum mismatch
This is on amd64/clang r249781, with ports at 317861: # pkg version -vX libgcry libgcrypt-1.5.0_1 < needs updating (port has 1.5.2) ===> License GPLv2 LGPL21 accepted by the user ===> libgcrypt-1.5.2 depends on file: /usr/local/sbin/pkg - found => libgcrypt-1.5.2.tar.bz2 doesn't seem to exist in /usr/ports/distfiles//. => Attempting to fetch http://gnupg.org.favoritelinks.net/libgcrypt/libgcrypt-1.5.2.tar.bz2 fetch: http://gnupg.org.favoritelinks.net/libgcrypt/libgcrypt-1.5.2.tar.bz2: size unknown fetch: http://gnupg.org.favoritelinks.net/libgcrypt/libgcrypt-1.5.2.tar.bz2: size of remote file is not known libgcrypt-1.5.2.tar.bz2 1082 B 2277 kBps 00m00s ===> Fetching all distfiles required by libgcrypt-1.5.2 for building ===> License GPLv2 LGPL21 accepted by the user ===> libgcrypt-1.5.2 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by libgcrypt-1.5.2 for building => SHA256 Checksum mismatch for libgcrypt-1.5.2.tar.bz2. ===> Giving up on fetching files: libgcrypt-1.5.2.tar.bz2 Make sure the Makefile and distinfo file (/usr/ports/security/libgcrypt/distinfo) are up to date. If you are absolutely sure you want to override this check, type "make NO_CHECKSUM=yes [other args]". *** [checksum] Error code 1 Stop in /usr/ports/security/libgcrypt. *** [checksum] Error code 1 Anton ___ 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: security/libgcrypt checksum mismatch
Hi, In message <201305111044.r4baimuh059...@mech-cluster241.men.bris.ac.uk>, Anton Shterenlikht (me...@bris.ac.uk) wrote: > This is on amd64/clang r249781, with ports at 317861: > > # pkg version -vX libgcry > libgcrypt-1.5.0_1 < needs updating (port has 1.5.2) > > ===> License GPLv2 LGPL21 accepted by the user > ===> libgcrypt-1.5.2 depends on file: /usr/local/sbin/pkg - found > => libgcrypt-1.5.2.tar.bz2 doesn't seem to exist in /usr/ports/distfiles//. > => Attempting to fetch > http://gnupg.org.favoritelinks.net/libgcrypt/libgcrypt-1.5.2.tar.bz2 > fetch: http://gnupg.org.favoritelinks.net/libgcrypt/libgcrypt-1.5.2.tar.bz2: > size unknown > fetch: http://gnupg.org.favoritelinks.net/libgcrypt/libgcrypt-1.5.2.tar.bz2: > size of remote file is not known > libgcrypt-1.5.2.tar.bz2 1082 B 2277 kBps 00m00s > ===> Fetching all distfiles required by libgcrypt-1.5.2 for building > ===> License GPLv2 LGPL21 accepted by the user > ===> libgcrypt-1.5.2 depends on file: /usr/local/sbin/pkg - found > ===> Fetching all distfiles required by libgcrypt-1.5.2 for building > => SHA256 Checksum mismatch for libgcrypt-1.5.2.tar.bz2. > ===> Giving up on fetching files: libgcrypt-1.5.2.tar.bz2 > Make sure the Makefile and distinfo file > (/usr/ports/security/libgcrypt/distinfo) > are up to date. If you are absolutely sure you want to override this > check, type "make NO_CHECKSUM=yes [other args]". > *** [checksum] Error code 1 > > Stop in /usr/ports/security/libgcrypt. > *** [checksum] Error code 1 I had something similar to this yesterday. Can you do the following and post the results here please? # file /usr/ports/distfiles/libgcrypt-1.5.2* In my case HTML files had been fetched! Cheers, Nick. -- ___ 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: security/libgcrypt checksum mismatch
I've been getting this with varying ports for some time now, sometimes I've had to manually fetch the distfiles. On 11/05/2013 12:01, N.J. Mann wrote: Hi, In message <201305111044.r4baimuh059...@mech-cluster241.men.bris.ac.uk>, Anton Shterenlikht (me...@bris.ac.uk) wrote: This is on amd64/clang r249781, with ports at 317861: # pkg version -vX libgcry libgcrypt-1.5.0_1 < needs updating (port has 1.5.2) ===> License GPLv2 LGPL21 accepted by the user ===> libgcrypt-1.5.2 depends on file: /usr/local/sbin/pkg - found => libgcrypt-1.5.2.tar.bz2 doesn't seem to exist in /usr/ports/distfiles//. => Attempting to fetch http://gnupg.org.favoritelinks.net/libgcrypt/libgcrypt-1.5.2.tar.bz2 fetch: http://gnupg.org.favoritelinks.net/libgcrypt/libgcrypt-1.5.2.tar.bz2: size unknown fetch: http://gnupg.org.favoritelinks.net/libgcrypt/libgcrypt-1.5.2.tar.bz2: size of remote file is not known libgcrypt-1.5.2.tar.bz2 1082 B 2277 kBps 00m00s ===> Fetching all distfiles required by libgcrypt-1.5.2 for building ===> License GPLv2 LGPL21 accepted by the user ===> libgcrypt-1.5.2 depends on file: /usr/local/sbin/pkg - found ===> Fetching all distfiles required by libgcrypt-1.5.2 for building => SHA256 Checksum mismatch for libgcrypt-1.5.2.tar.bz2. ===> Giving up on fetching files: libgcrypt-1.5.2.tar.bz2 Make sure the Makefile and distinfo file (/usr/ports/security/libgcrypt/distinfo) are up to date. If you are absolutely sure you want to override this check, type "make NO_CHECKSUM=yes [other args]". *** [checksum] Error code 1 Stop in /usr/ports/security/libgcrypt. *** [checksum] Error code 1 I had something similar to this yesterday. Can you do the following and post the results here please? # file /usr/ports/distfiles/libgcrypt-1.5.2* In my case HTML files had been fetched! Cheers, Nick. -- Regards, Gary J. Hayers g...@hayers.org PGP Signature http://www.hayers.org/pgp ___ 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: security/libgcrypt checksum mismatch
In message <518e2913.5040...@hayers.org>, Gary J. Hayers (g...@hayers.org) wrote: > I've been getting this with varying ports for some time now, sometimes > I've had to manually fetch the distfiles. I am sorry to hear this, but glad I am not the only one. :-) The files I have had to manually fetch are: libgcrypt-1.5.2.tar.bz2 libassuan-2.0.3.tar.bz2 libassuan-2.0.3.tar.bz2.sig libksba-1.3.0.tar.bz2 libksba-1.3.0.tar.bz2.sig gnupg-2.0.19.tar.bz2 gnupg-2.0.19.tar.bz2.sig gnupg-2.0.20.tar.bz2 gnupg-2.0.20.tar.bz2.sig Do you have a list of affected files/ports? Cheers, Nick. -- ___ 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: security/libgcrypt checksum mismatch
Seems very sporadic, gnupg-2.0.20.tar.bz2 and the .sig I had to manually fetch this morning. I have around 1000 ports installed and probably had to fetch around 50. libgcrypt-1.5.2.tar.bz2 is another so seems to be a pattern there. On 11/05/2013 12:52, N.J. Mann wrote: In message <518e2913.5040...@hayers.org>, Gary J. Hayers (g...@hayers.org) wrote: I've been getting this with varying ports for some time now, sometimes I've had to manually fetch the distfiles. I am sorry to hear this, but glad I am not the only one. :-) The files I have had to manually fetch are: libgcrypt-1.5.2.tar.bz2 libassuan-2.0.3.tar.bz2 libassuan-2.0.3.tar.bz2.sig libksba-1.3.0.tar.bz2 libksba-1.3.0.tar.bz2.sig gnupg-2.0.19.tar.bz2 gnupg-2.0.19.tar.bz2.sig gnupg-2.0.20.tar.bz2 gnupg-2.0.20.tar.bz2.sig Do you have a list of affected files/ports? Cheers, Nick. -- Regards, Gary J. Hayers g...@hayers.org PGP Signature http://www.hayers.org/pgp ___ 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"
repo copy (svn cp) gives pre-commit "Do not replace a file. This will break the CVS exporter."
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I though I could just do my own repo copies not, using svn copy in the ports tree. Is this just not allowed, due to the CVS exporter? Will I still have to request a repo copy from portmgr@? Palle -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJRjkaHAAoJEIhV+7FrxBJDtK4IAKIYyJWKlOOnDHqCI+UnNN56 AbPK15IeucfuSfnHQ98DB6JFQDZW6PAUkoxeWi3hANAI+ERh4ry7r0I1IYvKSzQe fyPhwqhffwMd1G5jnCVhQ1s9bQ7+x/+PdlW7g6szK5uImnN7uAXWX5YvujK+uf7l IOUOPB6NVtz3+tGl6hZY0jo5Ha+dASi9vqH/zYOvD+9NgVeWq6IskSIGvjdPQKkU zt+cSjdiJaQ433edTwRHkumK7xYkVTYW3shirAht2ZjbOACIbM7YVe2FLvY0sbFg 94akYgsLC0E/WSOEqr/K+gGyuCpdwJcmLaDLspl0YFB0S23gfxlLWOPUBpYAEVc= =5WPl -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"
FreeBSD ports you maintain which are out of date
Dear port maintainer, The portscout new distfile checker has detected that one or more of your ports appears to be out of date. Please take the opportunity to check each of the ports listed below, and if possible and appropriate, submit/commit an update. If any ports have already been updated, you can safely ignore the entry. You will not be e-mailed again for any of the port/version combinations below. Full details can be found at the following URL: http://portscout.freebsd.org/po...@freebsd.org.html Port| Current version | New version +-+ palm/synce-gvfs | 0.3.1 | 0.6 +-+ x11-wm/sawfish | 1.9.1 | 1.9.91 +-+ If any of the above results are invalid, please check the following page for details on how to improve portscout's detection and selection of distfiles on a per-port basis: http://portscout.freebsd.org/info/portscout-portconfig.txt If wish to stop receiving portscout reminders, please contact portsc...@portscout.freebsd.org Thanks. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: repo copy (svn cp) gives pre-commit "Do not replace a file. This will break the CVS exporter."
On 11 May 2013 14:24, Palle Girgensohn wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi, > > I though I could just do my own repo copies not, using svn copy in the > ports tree. Is this just not allowed, due to the CVS exporter? > > Will I still have to request a repo copy from portmgr@? Depends what you are repocopying from -> to. If you are copying a file over an existing file, that is disallowed (though why, I'm not sure-- I think the exporter hooks were left enabled even though we don't export any more). What are you trying to do? Chris ___ 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: security/libgcrypt checksum mismatch
In message <2013055228.gc94...@titania.njm.me.uk>, N.J. Mann (n...@njm.me.uk) wrote: > In message <518e2913.5040...@hayers.org>, > Gary J. Hayers (g...@hayers.org) wrote: > > I've been getting this with varying ports for some time now, sometimes > > I've had to manually fetch the distfiles. > > I am sorry to hear this, but glad I am not the only one. :-) > > The files I have had to manually fetch are: > > libgcrypt-1.5.2.tar.bz2 > libassuan-2.0.3.tar.bz2 > libassuan-2.0.3.tar.bz2.sig > libksba-1.3.0.tar.bz2 > libksba-1.3.0.tar.bz2.sig > gnupg-2.0.19.tar.bz2 > gnupg-2.0.19.tar.bz2.sig > gnupg-2.0.20.tar.bz2 > gnupg-2.0.20.tar.bz2.sig I now know why I get HTML files when trying to fetch these distfiles. The common factor is that they all use HTTP rather FTP for fetching. For HTTP fetches my ISP (British Telecom, aka BT) will display a "helpful" 'sorry no one at home' web page when the fetch fails, and that is what I end up with in the distfile. Thankfully, this 'nice' feature can be disabled. Once disabled 'make fetch' does its job of trying the next site after the failure and the proper file(s) are downloaded. I do not know whether other ISPs do something similar, does anyone? I wonder whether FTP sites should be listed before HTTP ones? Cheers, Nick. -- ___ 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: security/libgcrypt checksum mismatch
I'm on a brit ISP too, Virgin Media, not sure if they do something simular, I wonder if it is fetch(1) that is doing it, when manually downloading distfiles I use wget which shows no symptoms for downloading mismatch files... On 11/05/2013 14:59, N.J. Mann wrote: In message <2013055228.gc94...@titania.njm.me.uk>, I now know why I get HTML files when trying to fetch these distfiles. The common factor is that they all use HTTP rather FTP for fetching. For HTTP fetches my ISP (British Telecom, aka BT) will display a "helpful" 'sorry no one at home' web page when the fetch fails, and that is what I end up with in the distfile. Thankfully, this 'nice' feature can be disabled. Once disabled 'make fetch' does its job of trying the next site after the failure and the proper file(s) are downloaded. I do not know whether other ISPs do something similar, does anyone? I wonder whether FTP sites should be listed before HTTP ones? Cheers, Nick. -- Regards, Gary J. Hayers g...@hayers.org PGP Signature http://www.hayers.org/pgp ___ 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: repo copy (svn cp) gives pre-commit "Do not replace a file. This will break the CVS exporter."
Hi Chris, I did cd /usr/ports/databases svn cp postgresql90-server postgresql93-server and some then another set I'd similar copies. After that I modified the Makefiles and some other stuff. At commit it complained as per subject. Palle 11 maj 2013 kl. 15:36 skrev Chris Rees : > On 11 May 2013 14:24, Palle Girgensohn wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Hi, >> >> I though I could just do my own repo copies not, using svn copy in the >> ports tree. Is this just not allowed, due to the CVS exporter? >> >> Will I still have to request a repo copy from portmgr@? > > > Depends what you are repocopying from -> to. If you are copying a > file over an existing file, that is disallowed (though why, I'm not > sure-- I think the exporter hooks were left enabled even though we > don't export any more). > > What are you trying to do? > > Chris ___ 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: repo copy (svn cp) gives pre-commit "Do not replace a file. This will break the CVS exporter."
On 11 May 2013 15:29, Palle Girgensohn wrote: > Hi Chris, > > I did > > cd /usr/ports/databases > svn cp postgresql90-server postgresql93-server > > and some then another set I'd similar copies. After that I modified the > Makefiles and some other stuff. At commit it complained as per subject. Yes, it looks as though you've replaced a file with svn cp somehow. Unfortunately this kind of thing is incredibly fiddly... and some bugs can present in the svn pre-commit checks that break it. Your best bet is to do an old-fashioned svn cp postgresql90-server postgresql93-server, svn commit, then do the fiddling around with it all, as we used to in the cvs days. (Don't add it to databases/Makefile until it's ready of course!) If you run svn diff, you may even see which file you've "replaced". Chris > 11 maj 2013 kl. 15:36 skrev Chris Rees : > >> On 11 May 2013 14:24, Palle Girgensohn wrote: >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> Hi, >>> >>> I though I could just do my own repo copies not, using svn copy in the >>> ports tree. Is this just not allowed, due to the CVS exporter? >>> >>> Will I still have to request a repo copy from portmgr@? >> >> >> Depends what you are repocopying from -> to. If you are copying a >> file over an existing file, that is disallowed (though why, I'm not >> sure-- I think the exporter hooks were left enabled even though we >> don't export any more). >> >> What are you trying to do? >> >> Chris > ___ 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: repo copy (svn cp) gives pre-commit "Do not replace a file. This will break the CVS exporter."
Ok, thanks. That is probably exactly what happened. I'll check it out tomorrow. PostgreSQL 9.3 beta1 will be announced on Monday... :-) 11 maj 2013 kl. 16:54 skrev Chris Rees : > On 11 May 2013 15:29, Palle Girgensohn wrote: >> Hi Chris, >> >> I did >> >> cd /usr/ports/databases >> svn cp postgresql90-server postgresql93-server >> >> and some then another set I'd similar copies. After that I modified the >> Makefiles and some other stuff. At commit it complained as per subject. > > Yes, it looks as though you've replaced a file with svn cp somehow. > Unfortunately this kind of thing is incredibly fiddly... and some bugs > can present in the svn pre-commit checks that break it. > > Your best bet is to do an old-fashioned svn cp postgresql90-server > postgresql93-server, svn commit, then do the fiddling around with it > all, as we used to in the cvs days. (Don't add it to > databases/Makefile until it's ready of course!) > > If you run svn diff, you may even see which file you've "replaced". > > Chris > >> 11 maj 2013 kl. 15:36 skrev Chris Rees : >> >>> On 11 May 2013 14:24, Palle Girgensohn wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I though I could just do my own repo copies not, using svn copy in the ports tree. Is this just not allowed, due to the CVS exporter? Will I still have to request a repo copy from portmgr@? >>> >>> >>> Depends what you are repocopying from -> to. If you are copying a >>> file over an existing file, that is disallowed (though why, I'm not >>> sure-- I think the exporter hooks were left enabled even though we >>> don't export any more). >>> >>> What are you trying to do? >>> >>> Chris >> ___ 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: security/libgcrypt checksum mismatch
On Sat, 11 May 2013 14:59:46 +0100 "N.J. Mann" wrote: > In message <2013055228.gc94...@titania.njm.me.uk>, > N.J. Mann (n...@njm.me.uk) wrote: > > In message <518e2913.5040...@hayers.org>, > > Gary J. Hayers (g...@hayers.org) wrote: > > > I've been getting this with varying ports for some time now, > > > sometimes I've had to manually fetch the distfiles. > > > > I am sorry to hear this, but glad I am not the only one. :-) > > > > The files I have had to manually fetch are: > > > > libgcrypt-1.5.2.tar.bz2 > > libassuan-2.0.3.tar.bz2 > > libassuan-2.0.3.tar.bz2.sig > > libksba-1.3.0.tar.bz2 > > libksba-1.3.0.tar.bz2.sig > > gnupg-2.0.19.tar.bz2 > > gnupg-2.0.19.tar.bz2.sig > > gnupg-2.0.20.tar.bz2 > > gnupg-2.0.20.tar.bz2.sig > > I now know why I get HTML files when trying to fetch these distfiles. > The common factor is that they all use HTTP rather FTP for fetching. > For HTTP fetches my ISP (British Telecom, aka BT) will display a > "helpful" 'sorry no one at home' web page when the fetch fails, and > that is what I end up with in the distfile. Thankfully, this 'nice' > feature can be disabled. Once disabled 'make fetch' does its job of > trying the next site after the failure and the proper file(s) are > downloaded. > > I do not know whether other ISPs do something similar, does anyone? I > wonder whether FTP sites should be listed before HTTP ones? > > > Cheers, >Nick. Hi Nick, Besides the fact that ISPs really shouldn't interfere with your HTTP traffic in that way (terrible!), preferring FTP sounds like a bad idea, since it's a lot more complicated protocol and therefore more likely to fail in limited network setups. There are a couple of possible solutions, some more useful than others. 1. Avoid ISPs that break your traffic. Caveat: Sometimes you have no choice. 2. Use HTTPS whenever possible, so that certificate checking can take place and stop you from downloading broken files in the first place. (there's a patch to fetch I'm working on with des that will hopefully make it to base soon). Caveat: Not every project provides an SSL enabled source, lots of ports need to be adapted, never near 100%. 3. Modify the ports framework, so you can set an environment/config variable like PREFER_HTTP or PREFER_FTP. Caveat: It's work and not *that* useful. 4. Modify the ports framework, so it tries the next download location in case there is a file size or checksum mismatch. Caveat: Requires effort. IMHO implementing 4 would make a lot sense to compensate for broken mirrors. In the meantime, as a workaround, you could set HTTP_PROXY=127.0.0.1:12000 (or any other unused port on your system) That way fetch fails on all HTTP sites and therefore effectively uses FTP instead. Cheers, Michael -- Michael Gmelin ___ 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: WANTED: Tool to verify installed package/port consistancy
On 05/10/2013 03:04 PM, Ronald F. Guilmette wrote: > pkg_sanity: ImageMagick-6.8.0.7_1: +CONTENTS file does not exist -- skipped > pkg_sanity: ORBit2-2.14.19: /usr/local/lib/libORBit-2.so: File failed MD5 > checksum > pkg_sanity: ORBit2-2.14.19: /usr/local/lib/libORBit-imodule-2.so: File failed > MD5 checksum > pkg_sanity: ORBit2-2.14.19: /usr/local/lib/libORBitCosNaming-2.so: File > failed MD5 checksum > pkg_sanity: OpenEXR-1.7.1: /usr/local/lib/libIlmImf.so: File failed MD5 > checksum > pkg_sanity: aalib-1.4.r5_6: /usr/local/lib/libaa.so: File failed MD5 checksum Are these mismatches symlinks? If so, are you checking the contents of the symlink (with, for instance, stat(1) or readlink(1)), or the contents of the file to which the symlink is referring? -- Fuzzy love, -CyberLeo Technical Administrator CyberLeo.Net Webhosting http://www.CyberLeo.Net Furry Peace! - http://www.fur.com/peace/ ___ 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"
teTeX and TeXLive
Hello, As you already noticed, TeXLive ports have been imported and one can choose teTeX or TeXLive while the default value for pre-compiled packages is still teTeX. If you want to use TeXLive, please try to use the following knob: TEX_DEFAULT= texlive To do this, almost all of ports which use TeX will depend on TeXLive. Although some ports which install a new TeX macro package may not work because of incompatibility such as difference of directory structure between the two, ones which use TeX for typesetting should work fine. Ones to install macro packages which were non-standard in teTeX but are included in TeXLive will be fixed or removed. Please test TeXLive and send your failure report to me. Once it is confirmed that TEX_DEFAULT=texlive works, I will switch the default value from tetex to texlive at some point. -- Hiroki pgpPCKVZwk_YU.pgp Description: PGP signature
Re: TEX_DEFAULT problem
RyōTa SimaMoto wrote in : li> Hi, li> li> Please resolve %%TEXMFDIR%% of devel/tex-kpathsea/pkg-plist li> that could be once unfolded with definition at Mk/bsd.tex.mk li> which you unloaded. I have no idea where TEXMFDIR?="share/texmf" li> should be suggested and processed in the PLIST_SUB variable list li> when USE_TEX macro is unavailable. Should be fixed now. Thanks for the report. -- Hiroki pgpb2lCEGGVaI.pgp Description: PGP signature
Re: astro/gpsd fails to build on CURRENT
Rainer, On Tue, May 07, 2013 at 06:19:16PM +0200, Rainer Hurling wrote: R> When I try to build astro/gpsd on 10.0-CURRENT it fails with the R> following messages (devel/scons should be up to date): R> R> /usr/ports/astro/gpsd#make R> ===> Found saved configuration for gpsd-3.9 ... R> Checking for C header file sys/endian.h... yes R> Checking that xsltproc can make man pages... yes R> Altered configuration variables: R> mtk3301 = False (default True): MTK-3301 support R> nmea2000 = False (default True): NMEA2000/CAN support R> bluez = False (default True): BlueZ support for Bluetooth devices R> libQgpsmm = False (default True): build QT bindings R> chrpath = False (default True): use chrpath to edit library load paths R> mandir = man (default share/man): manual pages directory R> pkgconfig = libdata/pkgconfig (default lib/pkgconfig): pkgconfig file R> directory R> TypeError: Tried to lookup Dir '/usr/local/lib' as a File.: R> File "/usr/ports/astro/gpsd/work/gpsd-3.9/SConstruct", line 955: R> parse_flags=gpsdlibs + ncurseslibs + ['-lm']) R> File "/usr/local/lib/scons-2.1.0/SCons/Environment.py", line 258: R> return MethodWrapper.__call__(self, target, source, *args, **kw) R> File "/usr/local/lib/scons-2.1.0/SCons/Environment.py", line 222: R> return self.method(*nargs, **kwargs) R> File "/usr/local/lib/scons-2.1.0/SCons/Builder.py", line 631: R> env = env.Override(env_kw) R> File "/usr/local/lib/scons-2.1.0/SCons/Environment.py", line 635: R> if merges: env.MergeFlags(merges) R> File "/usr/local/lib/scons-2.1.0/SCons/Environment.py", line 810: R> args = self.ParseFlags(args) R> File "/usr/local/lib/scons-2.1.0/SCons/Environment.py", line 796: R> do_parse(arg) R> File "/usr/local/lib/scons-2.1.0/SCons/Environment.py", line 670: R> for t in arg: do_parse(t) R> File "/usr/local/lib/scons-2.1.0/SCons/Environment.py", line 726: R> dict['LIBS'].append(self.fs.File(arg)) R> File "/usr/local/lib/scons-2.1.0/SCons/Node/FS.py", line 1339: R> return self._lookup(name, directory, File, create) R> File "/usr/local/lib/scons-2.1.0/SCons/Node/FS.py", line 1318: R> return root._lookup_abs(p, fsclass, create) R> File "/usr/local/lib/scons-2.1.0/SCons/Node/FS.py", line 2223: R> result.must_be_same(klass) R> File "/usr/local/lib/scons-2.1.0/SCons/Node/FS.py", line 626: R> (self.__class__.__name__, self.path, klass.__name__)) R> *** [do-build] Error code 2 R> Stop in /usr/ports/astro/gpsd. R> *** [build] Error code 1 R> Stop in /usr/ports/astro/gpsd. Sorry, I can't reproduce that on a clean 10.0-CURRENT amd64. -- Totus tuus, Glebius. ___ 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: security/libgcrypt checksum mismatch
From n...@njm.me.uk Sat May 11 13:41:11 2013 In message <201305111044.r4baimuh059...@mech-cluster241.men.bris.ac.uk>, Anton Shterenlikht (me...@bris.ac.uk) wrote: > This is on amd64/clang r249781, with ports at 317861: > > # pkg version -vX libgcry > libgcrypt-1.5.0_1 < needs updating (port has 1.5.2) > > ===> License GPLv2 LGPL21 accepted by the user > ===> libgcrypt-1.5.2 depends on file: /usr/local/sbin/pkg - found > => libgcrypt-1.5.2.tar.bz2 doesn't seem to exist in /usr/ports/distfiles//. > => Attempting to fetch http://gnupg.org.favoritelinks.net/libgcrypt/libgcrypt-1.5.2.tar.bz2 > fetch: http://gnupg.org.favoritelinks.net/libgcrypt/libgcrypt-1.5.2.tar.bz2: size unknown > fetch: http://gnupg.org.favoritelinks.net/libgcrypt/libgcrypt-1.5.2.tar.bz2: size of remote file is not known > libgcrypt-1.5.2.tar.bz2 1082 B 2277 kBps 00m00s > ===> Fetching all distfiles required by libgcrypt-1.5.2 for building > ===> License GPLv2 LGPL21 accepted by the user > ===> libgcrypt-1.5.2 depends on file: /usr/local/sbin/pkg - found > ===> Fetching all distfiles required by libgcrypt-1.5.2 for building > => SHA256 Checksum mismatch for libgcrypt-1.5.2.tar.bz2. > ===> Giving up on fetching files: libgcrypt-1.5.2.tar.bz2 > Make sure the Makefile and distinfo file (/usr/ports/security/libgcrypt/distinfo) > are up to date. If you are absolutely sure you want to override this > check, type "make NO_CHECKSUM=yes [other args]". > *** [checksum] Error code 1 > > Stop in /usr/ports/security/libgcrypt. > *** [checksum] Error code 1 I had something similar to this yesterday. Can you do the following and post the results here please? # file /usr/ports/distfiles/libgcrypt-1.5.2* In my case HTML files had been fetched! # file /usr/ports/distfiles/libgcrypt-1.5.2* /usr/ports/distfiles/libgcrypt-1.5.2.tar.bz2: HTML document, ASCII text, with very long lines, with no line terminators # yes, silly.. But did you manage to get the right file afterwards? Thanks Anton ___ 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: xfce4-weather-plugin: crash
2013/5/9 Andriy Kornatskyy > Whom can I send a crash dump? > Are you able to host crash dump somewhere ? > > Thanks. > > Andriy Kornatskyy > ___ > 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" > -- olivier ___ 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: WANTED: Tool to verify installed package/port consistancy
In message <518e1a51.3020...@cyberleo.net>, you wrote: >On 05/10/2013 03:04 PM, Ronald F. Guilmette wrote: > >> pkg_sanity: ImageMagick-6.8.0.7_1: +CONTENTS file does not exist -- skipped >> pkg_sanity: ORBit2-2.14.19: /usr/local/lib/libORBit-2.so: File failed MD5 >> checksum >> pkg_sanity: ORBit2-2.14.19: /usr/local/lib/libORBit-imodule-2.so: File >> failed MD5 checksum >> pkg_sanity: ORBit2-2.14.19: /usr/local/lib/libORBitCosNaming-2.so: File >> failed MD5 checksum >> pkg_sanity: OpenEXR-1.7.1: /usr/local/lib/libIlmImf.so: File failed MD5 >> checksum >> pkg_sanity: aalib-1.4.r5_6: /usr/local/lib/libaa.so: File failed MD5 checksum > > >Are these mismatches symlinks? Some are. >If so, are you checking the contents of >the symlink (with, for instance, stat(1) or readlink(1)), or the >contents of the file to which the symlink is referring? The latter. (I would have had to have done something special in order to compute the md5 fo teh symlink itself, and I did not do so. I have just now checked, and my script is indeed getting the md5 of the files to which the various symlinks refer.) It is clear to me now that "pkg_info -g" is either skipping certain files that are listed in the relevant +CONTENTS files or else it is computing the MD5 checksums in an odd way. I do not think that the latter possibility is at all likely. I will be looking at this more deeply as time permits. Regards, rfg ___ 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: ports/119546
On 5/11/13, Andrea Venturoli wrote:
> On 05/10/13 15:50, b.f. wrote:
...
> Here's what I did:
> # find /usr/ports -type f -exec grep -l OPENSS_PORT "{}" ";"
>
> This showed very few ports really requiring openssl from ports, none of
> which I had currently installed.
>
Then the simplest and safest solution for you is just to remove
security/openssl, if you don't think that you'll need it.
> So I moved its libraries to /usr/local/lib/compat/pkg/ and pkg_deleted
> (-f) it. Newer compilations would pick up base, then.
>
You may also need to move the security/openssl headers out of
${LOCALBASE}/include/openssl, to prevent ports from mistakenly using
them.
...
b.
___
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: astro/gpsd fails to build on CURRENT
## Gleb Smirnoff (gleb...@freebsd.org): > Sorry, I can't reproduce that on a clean 10.0-CURRENT amd64. Is devel/ncurses installed on your machine? As explained previously, scons mis-parses the output of ncurses5-config; and astro/gpsd build just fine after modifying ncurses5-config. Regards, Christoph -- Spare Space ___ 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: security/libgcrypt checksum mismatch
On Sat, 11 May 2013 17:39:52 +0200
Michael Gmelin wrote:
> Besides the fact that ISPs really shouldn't interfere with your HTTP
> traffic in that way (terrible!), preferring FTP sounds like a bad
> idea, since it's a lot more complicated protocol and therefore more
> likely to fail in limited network setups. There are a couple of
> possible solutions, some more useful than others.
I doubt it makes much difference, fetch can request ftp urls through
an http proxy which eliminates a lot of the potential problems, and
even in the worst case FreeBSD will fall through to an HTTP link.
> 1. Avoid ISPs that break your traffic.
>Caveat: Sometimes you have no choice.
> 2. Use HTTPS whenever possible, so that certificate checking can take
>place and stop you from downloading broken files in the first
> place. (there's a patch to fetch I'm working on with des that will
>hopefully make it to base soon).
>Caveat: Not every project provides an SSL enabled source, lots of
>ports need to be adapted, never near 100%.
On the whole caching is a good thing. HTTPS sounds more trouble than
it's worth to me.
> 3. Modify the ports framework, so you can set an environment/config
>variable like PREFER_HTTP or PREFER_FTP.
>Caveat: It's work and not *that* useful.
You can already do this with:
MASTER_SORT_REGEX?= ^ftp:
I used to do it the other way around because my ISP preferred cached
HTTP in their traffic shaping.
> 4. Modify the ports framework, so it tries the next download location
>in case there is a file size or checksum mismatch.
>Caveat: Requires effort.
>
> IMHO implementing 4 would make a lot sense to compensate for broken
> mirrors.
FWIW I fetch files like this:
for porg in `pkg version -Iol'<' |awk '{ print $1 }'` ; do
echo "Checking - ${porg}"
cd /usr/ports/${porg}
make checksum || (
export RANDOMIZE_MASTER_SITES=yes
make distclean
make checksum
)
done
I do it that way because it avoids a lot of problems with rerolled
files, but it would help with this problem too.
___
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: astro/gpsd fails to build on CURRENT
On Sat, May 11, 2013 at 10:05:22PM +0200, Rainer Hurling wrote: R> On 11.05.2013 20:53 (UTC+2), Gleb Smirnoff wrote: R> > Rainer, R> > R> > On Tue, May 07, 2013 at 06:19:16PM +0200, Rainer Hurling wrote: R> > R> When I try to build astro/gpsd on 10.0-CURRENT it fails with the R> > R> following messages (devel/scons should be up to date): R> > R> R> > R> /usr/ports/astro/gpsd#make R> > R> ===> Found saved configuration for gpsd-3.9 R> > R> > ... R> > R> > R> Checking for C header file sys/endian.h... yes R> > R> Checking that xsltproc can make man pages... yes R> > R> Altered configuration variables: R> > R> mtk3301 = False (default True): MTK-3301 support R> > R> nmea2000 = False (default True): NMEA2000/CAN support R> > R> bluez = False (default True): BlueZ support for Bluetooth devices R> > R> libQgpsmm = False (default True): build QT bindings R> > R> chrpath = False (default True): use chrpath to edit library load paths R> > R> mandir = man (default share/man): manual pages directory R> > R> pkgconfig = libdata/pkgconfig (default lib/pkgconfig): pkgconfig file R> > R> directory R> > R> TypeError: Tried to lookup Dir '/usr/local/lib' as a File.: R> > R> File "/usr/ports/astro/gpsd/work/gpsd-3.9/SConstruct", line 955: R> > R> parse_flags=gpsdlibs + ncurseslibs + ['-lm']) R> > R> File "/usr/local/lib/scons-2.1.0/SCons/Environment.py", line 258: R> > R> return MethodWrapper.__call__(self, target, source, *args, **kw) R> > R> File "/usr/local/lib/scons-2.1.0/SCons/Environment.py", line 222: R> > R> return self.method(*nargs, **kwargs) R> > R> File "/usr/local/lib/scons-2.1.0/SCons/Builder.py", line 631: R> > R> env = env.Override(env_kw) R> > R> File "/usr/local/lib/scons-2.1.0/SCons/Environment.py", line 635: R> > R> if merges: env.MergeFlags(merges) R> > R> File "/usr/local/lib/scons-2.1.0/SCons/Environment.py", line 810: R> > R> args = self.ParseFlags(args) R> > R> File "/usr/local/lib/scons-2.1.0/SCons/Environment.py", line 796: R> > R> do_parse(arg) R> > R> File "/usr/local/lib/scons-2.1.0/SCons/Environment.py", line 670: R> > R> for t in arg: do_parse(t) R> > R> File "/usr/local/lib/scons-2.1.0/SCons/Environment.py", line 726: R> > R> dict['LIBS'].append(self.fs.File(arg)) R> > R> File "/usr/local/lib/scons-2.1.0/SCons/Node/FS.py", line 1339: R> > R> return self._lookup(name, directory, File, create) R> > R> File "/usr/local/lib/scons-2.1.0/SCons/Node/FS.py", line 1318: R> > R> return root._lookup_abs(p, fsclass, create) R> > R> File "/usr/local/lib/scons-2.1.0/SCons/Node/FS.py", line 2223: R> > R> result.must_be_same(klass) R> > R> File "/usr/local/lib/scons-2.1.0/SCons/Node/FS.py", line 626: R> > R> (self.__class__.__name__, self.path, klass.__name__)) R> > R> *** [do-build] Error code 2 R> > R> Stop in /usr/ports/astro/gpsd. R> > R> *** [build] Error code 1 R> > R> Stop in /usr/ports/astro/gpsd. R> R> Gleb, R> R> thanks for answering. R> R> > R> > Sorry, I can't reproduce that on a clean 10.0-CURRENT amd64. R> > R> For me this happens on three boxes, all 10.0-CURRENT amd64 with more R> than 1.500 ports installed (most because of their use for scientific R> workplaces, some multimedia ones). R> R> I think Christoph is right here in suspecting scons interaction with R> ncurses (wrong parsing). If I patch /usr/local/bin/ncurses5-config in R> the way, Christoph suggested, all went fine. The attached zip contains R> two log files, one with the messages of the unpatched build, one with R> the patched one. R> R> My systems are far away from 'clean' systems, because they growed over R> the years. On the other hand, even if I try to build astro/gpsd without R> /etc/make.conf, it fails. I have no clue, where to look next. May be maintainer of scons has idea. I've added him to Cc. -- Totus tuus, Glebius. ___ 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: teTeX and TeXLive
Hiroki Sato writes: > Once it is confirmed that TEX_DEFAULT=texlive works, I will switch > the default value from tetex to texlive at some point. Thanks a lot for all the work. Is removing tetex a middle or long-term goal? ___ 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: repo copy (svn cp) gives pre-commit "Do not replace a file. This will break the CVS exporter."
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ah yes, thanks, that did the trick. Thanks! :) Palle Palle Girgensohn skrev: > Ok, thanks. That is probably exactly what happened. I'll check it out > tomorrow. > > PostgreSQL 9.3 beta1 will be announced on Monday... :-) > > 11 maj 2013 kl. 16:54 skrev Chris Rees : > >> On 11 May 2013 15:29, Palle Girgensohn >> wrote: >>> Hi Chris, >>> >>> I did >>> >>> cd /usr/ports/databases svn cp postgresql90-server >>> postgresql93-server >>> >>> and some then another set I'd similar copies. After that I >>> modified the Makefiles and some other stuff. At commit it >>> complained as per subject. >> Yes, it looks as though you've replaced a file with svn cp >> somehow. Unfortunately this kind of thing is incredibly fiddly... >> and some bugs can present in the svn pre-commit checks that break >> it. >> >> Your best bet is to do an old-fashioned svn cp postgresql90-server >> postgresql93-server, svn commit, then do the fiddling around with >> it all, as we used to in the cvs days. (Don't add it to >> databases/Makefile until it's ready of course!) >> >> If you run svn diff, you may even see which file you've >> "replaced". >> >> Chris >> >>> 11 maj 2013 kl. 15:36 skrev Chris Rees : >>> On 11 May 2013 14:24, Palle Girgensohn wrote: > -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > Hi, > > I though I could just do my own repo copies not, using svn > copy in the ports tree. Is this just not allowed, due to the > CVS exporter? > > Will I still have to request a repo copy from portmgr@? Depends what you are repocopying from -> to. If you are copying a file over an existing file, that is disallowed (though why, I'm not sure-- I think the exporter hooks were left enabled even though we don't export any more). What are you trying to do? Chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJRjt0EAAoJEIhV+7FrxBJDdiwIAIvOl11o8TRJPiYOWNoulFRa Qa9lN7lml1VzneBXMtsJmEKHGngtJFtSspFtp82flL/PczI2zZ/ro02Iw7wVqQjq feV19FSv9UPJ1FlJdZQRMypUirof08ryoW+N9OAfzqRU33rUREq89N0FavnanyN9 svqouX1c5pITR2vUhVXX3enizlWAabmjMbT/lJLLBqpaE8l5XBEZ8j4biQr9ovvK 7FMvuPgdxGdiy9haz95/6TH9dy5a5UXB0NFQE/+5Y61U/SERohEw8bWMAU3n6u9b Idi0Qvf1aeBSioBF8TH3nyt7+6qqYF+P1mgDI/8FWiSGn5uzdBjgAdc70nGps6c= =W5YO -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"
[QAT] r317925: 32x leftovers
Add postgresql 9.3 beta1 - Build ID: 20130512000200-31314 Job owner: gir...@freebsd.org Buildtime: 79 minutes Enddate: Sun, 12 May 2013 01:21:12 GMT Revision: r317925 Repository: https://svnweb.freebsd.org/ports?view=revision&revision=317925 - Port:databases/postgresql93-client 9.3.b1 Buildgroup: 9.1-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137612/postgresql-client-9.3.b1.log Buildgroup: 9.1-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137613/postgresql-client-9.3.b1.log Buildgroup: 8.3-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137614/postgresql-client-9.3.b1.log Buildgroup: 8.3-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137615/postgresql-client-9.3.b1.log - Port:databases/postgresql93-contrib 9.3.b1 Buildgroup: 9.1-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137616/postgresql-contrib-9.3.b1.log Buildgroup: 9.1-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137617/postgresql-contrib-9.3.b1.log Buildgroup: 8.3-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137618/postgresql-contrib-9.3.b1.log Buildgroup: 8.3-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137619/postgresql-contrib-9.3.b1.log - Port:databases/postgresql93-docs 9.3.b1 Buildgroup: 9.1-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137620/postgresql-docs-9.3.b1.log Buildgroup: 9.1-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137621/postgresql-docs-9.3.b1.log Buildgroup: 8.3-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137622/postgresql-docs-9.3.b1.log Buildgroup: 8.3-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137623/postgresql-docs-9.3.b1.log - Port:databases/postgresql93-pgtcl 2.0.0 Buildgroup: 9.1-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137624/pgtcl-postgresql93-2.0.0.log Buildgroup: 9.1-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137625/pgtcl-postgresql93-2.0.0.log Buildgroup: 8.3-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137626/pgtcl-postgresql93-2.0.0.log Buildgroup: 8.3-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137627/pgtcl-postgresql93-2.0.0.log - Port:databases/postgresql93-plperl 9.3.b1 Buildgroup: 9.1-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137628/postgresql-plperl-9.3.b1.log Buildgroup: 9.1-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137629/postgresql-plperl-9.3.b1.log Buildgroup: 8.3-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137630/postgresql-plperl-9.3.b1.log Buildgroup: 8.3-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137631/postgresql-plperl-9.3.b1.log - Port:databases/postgresql93-plpython 9.3.b1 Buildgroup: 9.1-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~gir...@freebsd.org/20130512000200-31314-137632/postgresql-plpython-9.3.b1.log Buildg
