pkg periodic with proxy
Hello. /usr/local/etc/periodic/security/410.pkg-audit is failing with: pkg: http://www.vuxml.org/freebsd/vuln.xml.bz2: Permission denied pkg: cannot fetch vulnxml file The reason is that this machine needs to go through a proxy; in fact it works if I launch it manually (where I have HTTP_PROXY set). How to deal with this without modifying the script itself? 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: pkg periodic with proxy
On 14 Aug 2014, at 08:58, Andrea Venturoli m...@netfence.it wrote: Hello. /usr/local/etc/periodic/security/410.pkg-audit is failing with: pkg: http://www.vuxml.org/freebsd/vuln.xml.bz2: Permission denied pkg: cannot fetch vulnxml file The reason is that this machine needs to go through a proxy; in fact it works if I launch it manually (where I have HTTP_PROXY set). How to deal with this without modifying the script itself? I worked around this here by setting HTTP_PROXY in /etc/crontab. You could also set it in /usr/local/etc/pkg.conf by using PKG_ENV. I didn't, because I run my own repo and I only want a proxy for pkg audit. 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 ___ 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 +-+ net-mgmt/pandorafms_agent | 4.0.1 | 5.1-140814 +-+ net-mgmt/pandorafms_console | 4.0.1 | 5.1-140814 +-+ net-mgmt/pandorafms_server | 4.0.1 | 5.1-140814 +-+ www/groupoffice | 3.7.24 | 6.0.15 +-+ 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 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
installing packages into a mounted system
Hello, I've compiled ~1300 packages with poudriere 3.1pre on a 'head' system; went fine; mounted below /mnt is a complete new system (an USB key) which boots fine alreaday; the 1300 resulting *.txz file are copied into /mnt/PKGDIR in the past, using the pkg_* tools, I could just install the packages with: # PKG_PATH=/PKGDIR # export PKG_PATH # chroot /mnt pkg_add xorg-7.7 # chroot /mnt pkg_add kde-4.10.5 ... How this can be done now with pkg(8)? I thought I will compile a pkg-static and move this to into the /mnt system too with # chroot /mnt mkdir -p /usr/local/sbin # cp -p /usr/local/sbin/pkg-static /mnt/usr/local/sbin pkg-static(8) works there, bringing up the help with: # chroot /mnt /usr/local/sbin/pkg-static help But, how do I specify that it should install for example xorg-7.7 having its file (and all others) in /mnt/PKGDIR/xorg-7.7.txz It seems to look for some files digests.txz or repo.txz which I do not have: # PACKAGESITE=file://PKGDIR export PACKAGESITE # chroot /mnt /usr/local/sbin/pkg-static install xorg-7.7 Updating repository catalogue pkg-static: file://PKGDIR/digests.txz: No such file or directory pkg-static: No digest falling back on legacy catalog format pkg-static: file://PKGDIR/repo.txz: No such file or directory Any hints? Thx matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ 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: installing packages into a mounted system
On 08/14/14 09:18, Matthias Apitz wrote: Hello, I've compiled ~1300 packages with poudriere 3.1pre on a 'head' system; went fine; mounted below /mnt is a complete new system (an USB key) which boots fine alreaday; the 1300 resulting *.txz file are copied into /mnt/PKGDIR in the past, using the pkg_* tools, I could just install the packages with: # PKG_PATH=/PKGDIR # export PKG_PATH # chroot /mnt pkg_add xorg-7.7 # chroot /mnt pkg_add kde-4.10.5 ... How this can be done now with pkg(8)? I thought I will compile a pkg-static and move this to into the /mnt system too with # chroot /mnt mkdir -p /usr/local/sbin # cp -p /usr/local/sbin/pkg-static /mnt/usr/local/sbin pkg-static(8) works there, bringing up the help with: # chroot /mnt /usr/local/sbin/pkg-static help But, how do I specify that it should install for example xorg-7.7 having its file (and all others) in /mnt/PKGDIR/xorg-7.7.txz It seems to look for some files digests.txz or repo.txz which I do not have: # PACKAGESITE=file://PKGDIR export PACKAGESITE # chroot /mnt /usr/local/sbin/pkg-static install xorg-7.7 Updating repository catalogue pkg-static: file://PKGDIR/digests.txz: No such file or directory pkg-static: No digest falling back on legacy catalog format pkg-static: file://PKGDIR/repo.txz: No such file or directory Any hints? Thx matthias From the man page: pkg [-v] [-d] [-l] [-N] [-j jail name or id | -c chroot path] You could try copying pkg-static inside the chroot and use pkg-static -c (from the host, don't invoke the chroot command manually). I have been installing packages to jails this way for a while. - Nikolai Lifanov ___ 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: installing packages into a mounted system
El día Thursday, August 14, 2014 a las 09:22:38AM -0400, Nikolai Lifanov escribió: # PACKAGESITE=file://PKGDIR export PACKAGESITE # chroot /mnt /usr/local/sbin/pkg-static install xorg-7.7 Updating repository catalogue pkg-static: file://PKGDIR/digests.txz: No such file or directory pkg-static: No digest falling back on legacy catalog format pkg-static: file://PKGDIR/repo.txz: No such file or directory From the man page: pkg [-v] [-d] [-l] [-N] [-j jail name or id | -c chroot path] You could try copying pkg-static inside the chroot and use pkg-static -c (from the host, don't invoke the chroot command manually). I have been installing packages to jails this way for a while. # pkg-static -c /mnt install xorg-7.7 gives the same error messages as above. Thanks matthias -- Matthias Apitz | /\ ASCII Ribbon Campaign: E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail WWW: http://www.unixarea.de/ | X- No proprietary attachments phone: +49-170-4527211 | / \ - Respect for open standards | en.wikipedia.org/wiki/ASCII_Ribbon_Campaign ___ 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: installing packages into a mounted system
On Thu, 14 Aug 2014 15:31:11 +0200 Matthias Apitz g...@unixarea.de wrote: El día Thursday, August 14, 2014 a las 09:22:38AM -0400, Nikolai Lifanov escribió: # PACKAGESITE=file://PKGDIR export PACKAGESITE # chroot /mnt /usr/local/sbin/pkg-static install xorg-7.7 Updating repository catalogue pkg-static: file://PKGDIR/digests.txz: No such file or directory pkg-static: No digest falling back on legacy catalog format pkg-static: file://PKGDIR/repo.txz: No such file or directory From the man page: pkg [-v] [-d] [-l] [-N] [-j jail name or id | -c chroot path] You could try copying pkg-static inside the chroot and use pkg-static -c (from the host, don't invoke the chroot command manually). I have been installing packages to jails this way for a while. # pkg-static -c /mnt install xorg-7.7 gives the same error messages as above. Did you run pkg repo on your repo, e.g. cd mypackerepodir pkg repo . If you don't want to use a repo you could also use pkg add, e.g. cd $PKGDIR pkg add xorg-7.7.txz -- 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: net-im/skype-[devel] won't connect
The problem not in the skype. The problem in the linux pulse audio libs. I try to setup pulse audio server on freebsd and configure to tcp/ip protocol - works fine. But linux pulse client with the same config don't work (I tried simple console utils). I don't know how to trace problem. But possible pulse audio libs require some missing lib (open by dlopen) On Wednesday 13 August 2014 22:09:22 Vassilis Laganakos wrote: Hi, On Wed, Aug 13, 2014 at 10:47:25AM -0500, Scot Hetzel wrote: On Wed, Aug 13, 2014 at 10:38 AM, Kenta S. ken...@hush.com wrote: Hello. This afternoon when I try to sign onto Skype, I get: Periodic UIC Update Failed I haven't updated ports recently. Does anyone have an idea? I heard Skype was closing down old versions. I had received the following e-mail from Skype a few days ago: On Fri, Aug 8, 2014 at 7:53 PM, Skype norep...@emails.skype.com wrote: Your Skype for Linux version is being retired. Update today. » Can't see this email properly? Forgotten your password? Your Skype for Linux version is being retired. Update today. Dear swhetzel, We are now retiring older versions of Skype and it appears that at some point you signed into Skype with one of these. To continue signing into Skype on Linux you'll need to download the latest version. The new version comes with improved performance, the latest features and security updates, so you'll get the best possible Skype experience. If you're on the latest version of Skype, the above will not apply. Update now at http://www.skype.com/download. Someone will need to update the Skype port to the latest Linux version and see if it works on our current version of Linux emulation. I've read in various places (and tested myself with a couple of version on Linux) that any version before skype 4.3.0.37 will not connect. The skype port at: https://github.com/vassilisl/freebsd-ports/tree/master/net-im/skype4 will connect (if you use the f20 ports https://github.com/vassilisl/freebsd-linux_base-f20 ;) ) but it doesn't have sound working. Both xmj and I are working on getting that version of Skype on c6 and f20 linux emulation bases respectivelly, which basically means get it to talk to pulseaudio. If anyone has experience with that, please shout! :) Regards, Vassilis -- Artyom Mirgorodskiy ___ 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: pkg-static error when installing php5 from ports
On 8/13/2014 9:07 PM, Neel Natu wrote: No response on freebsd-pkg@ so figured I would try my luck here. best Neel On Tue, Aug 12, 2014 at 5:57 PM, Neel Natu neeln...@gmail.com wrote: Hi, I am installing php5 from ports. It builds fine but fails with this error when installing: [/usr/ports/lang/php5]$ sudo make install === Installing for php5-5.4.31 === php5-5.4.31 depends on shared library: libpcre.so - found (/usr/local/lib/libpcre.so.3) === php5-5.4.31 depends on shared library: libxml2.so - found (/usr/local/lib/libxml2.so.2.9.1) === Checking if php5 already installed === Registering installation for php5-5.4.31 pkg-static: Invalid manifest format: could not find expected ':' *** Error code 74 Stop. make[1]: stopped in /usr/ports/lang/php5 *** Error code 1 Any clue what might be happening and how to fix? best Neel This came up in #pkgng on freenode as well. Your Pkg is probably too old. Check with 'pkg -v'. The current release is at 1.3.6 now. You're likely running 1.1. Upgrade Pkg to support the new JSON format for the manifest. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: pkg-static error when installing php5 from ports
On 8/14/2014 9:30 AM, Bryan Drewery wrote: On 8/13/2014 9:07 PM, Neel Natu wrote: No response on freebsd-pkg@ so figured I would try my luck here. best Neel On Tue, Aug 12, 2014 at 5:57 PM, Neel Natu neeln...@gmail.com wrote: Hi, I am installing php5 from ports. It builds fine but fails with this error when installing: [/usr/ports/lang/php5]$ sudo make install === Installing for php5-5.4.31 === php5-5.4.31 depends on shared library: libpcre.so - found (/usr/local/lib/libpcre.so.3) === php5-5.4.31 depends on shared library: libxml2.so - found (/usr/local/lib/libxml2.so.2.9.1) === Checking if php5 already installed === Registering installation for php5-5.4.31 pkg-static: Invalid manifest format: could not find expected ':' *** Error code 74 Stop. make[1]: stopped in /usr/ports/lang/php5 *** Error code 1 Any clue what might be happening and how to fix? best Neel This came up in #pkgng on freenode as well. Your Pkg is probably too old. Check with 'pkg -v'. The current release is at 1.3.6 now. You're likely running 1.1. Upgrade Pkg to support the new JSON format for the manifest. We should add a version check to bsd.port.mk for Pkg. 1.2.0+ is required for Ports currently. Care needs to be taken to not initiate the bootstrap. So only executing LOCALBASE/sbin/pkg -v iff it exists. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: [Patch] Using MACHINE_ARCH identifiers in pkg
On 5/28/2014 11:54 AM, Nathan Whitehorn wrote: The current/previous values are also kept so that the patched pkg can install a package marked either with an x86:64 or amd64-type architecture ID (symlinks will be needed for a little bit on the package server to allow both clients to work). Limited testing suggests it works well -- I can fetch and install packages fine. More testing would be great. Symlinks are now setup to make testing of this easier. I'll let Bapt signoff on this patch officially and its timeframe. It seems reasonable to me. The use of 'x86' almost caused a regression recently due to its ambiguity. Cheers, Bryan signature.asc Description: OpenPGP digital signature
Re: pkg 1.3.5.1 -1.3.6: Repository has incompatible checksum format, need to re-create database
On 8/13/2014 8:15 PM, Russell L. Carter wrote: On 08/13/14 17:59, Koichiro IWAO wrote: Try `pkg update`. It might be `pkg update -f`. That seems to work, perhaps the message might read, Repository needs to be updated, run \pkg update\ or Repository has incompatible checksum format, see pkg-update Thanks! Russell Good idea. I've updated the wording for the next release. Bryan signature.asc Description: OpenPGP digital signature
devel/doxygen texlive dependency missing
Hello :-) I have just built the comms/usrp port and it turned out the documentation was missing so the port could not install. This was because LaTeX was missing on my system. After I have installed TeXLive build was fine. Doxygen depends on LaTeX and the dependency is missing. TeTeX seems to be abandoned, therefore TeXLive dependency should be added. Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ 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: redports and build status
On Wed, Aug 13, 2014 at 7:00 PM, Carlos Jacobo Puga Medina c...@fbsd.es wrote: On Wed, 13 Aug 2014 17:11:28 +0200 Fernando Apestegu=C3=ADa wrote: Mine is modified but nothing to do with dependencies or such. However this problem is reproducible. This is the port: https://redports.org/browser/fernape/lang/basic256?rev=3D30358 I don't see very bad things there or at least not compared with the previous revision which finished with success Can you think of anything I can try? I'm willing to help. I got used to run successfully tests in redports to attach them to my PR's and I don't want to update this port until it builds properly. Regards Hi Fernando, It's just a shot in the dark, but try to delete the content of your SVN repository then re-add all your ports again. Done. Still same effect. Cheers, -- Carlos Jacobo Puga Medina c...@fbsd.es ___ 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 marked IGNORE
On Wed, Aug 13, 2014 at 5:00 AM, Kurt Jaeger li...@opsec.eu wrote: Hi! While running portupgrade -a, I found the following ports were marked as IGNORE: - print/acroread9 (marked as IGNORE) - ftp/linux-f10-curl (marked as IGNORE) - textproc/linux-f10-expat (marked as IGNORE) - security/linux-f10-gnutls (marked as IGNORE) - security/linux-f10-libgcrypt (marked as IGNORE) - textproc/linux-f10-libxml2 (marked as IGNORE) - security/linux-f10-nss (marked as IGNORE) - net/linux-f10-openldap (marked as IGNORE) - security/linux-f10-openssl (marked as IGNORE) - graphics/linux-f10-png (marked as IGNORE) - graphics/linux-f10-tiff (marked as IGNORE) Are there any plains to update/correct these programs? Not those, they are part of really ancient linux packages which provide part of a linux emulation environment. f10 == Fedora 10. Here is more info on the state of the linux emu, there is work being done to update it to fedora 19 or 20, centos 6 or 7 and some more recent linux-kernel emulation (even for 64bit linux). https://wiki.freebsd.org/201407DevSummit/LinuxEmulation Also, what is suppose to replace print/acroread9? I need that program or something that works similar to it. Acrobat itself no longer supports acroread9, and 10+11 are not provided for linux anymore. So: It's a real issue, and I know no solution. I use xpdf for most PDF stuff. There are other PDF display programs but as far as I understand, most use the same core (poppler). There is graphics/mupdf, which probably uses a different core, maybe it does what you need ? -- p...@opsec.eu+49 171 3101372 6 years to go ! For several years I have been using evince for PDF display. It's MUCH lighter weight than Acrobat and works very well. It is poppler based and will probably pull in a LOT of Gnome stuff, so it is best if you already run Gnome, MATE, or have ports installed that have already pulled in the main Gnome2 libraries. -- 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: [Patch] Using MACHINE_ARCH identifiers in pkg
On 08/14/14 08:02, Bryan Drewery wrote: On 5/28/2014 11:54 AM, Nathan Whitehorn wrote: The current/previous values are also kept so that the patched pkg can install a package marked either with an x86:64 or amd64-type architecture ID (symlinks will be needed for a little bit on the package server to allow both clients to work). Limited testing suggests it works well -- I can fetch and install packages fine. More testing would be great. Symlinks are now setup to make testing of this easier. I'll let Bapt signoff on this patch officially and its timeframe. It seems reasonable to me. The use of 'x86' almost caused a regression recently due to its ambiguity. Cheers, Bryan Thanks Bryan! If anyone is interested in testing the adapted pkg, there is a patch that can be applied to ports at http://people.freebsd.org/~nwhitehorn/pkg-new-abi.diff. It tries to make this transition as painless as possible by doing the following things: 1. Have pkg use e.g. FreeBSD:11:amd64 instead of freebsd:11:x86:64 as an ABI string. 2. Maintain the freebsd:11:x86:64-type strings as the altabi config variable. 3. pkg will install packages where the architecture ID matches either the ABI or ALTABI value, which means that new pkg can install packages made with the older version. 4. Patches the ports-mgmt/pkg Makefile so that the package for pkg itself is given a freebsd:11:x86:64-type architecture. This prevents pkg from choking on an update to itself and should, with the symlinks discussed above, make the transition painless and transparent. Especially point (4) I'd appreciate testing on if anyone is generating private package repositories. -Nathan ___ 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
devel/doxygen woes
So I've been getting a lot of issues being directed at me due to the recent devel/doxygen update to 1.8.7. While I'm not sure why these issues only cropped up after that update and not before, I would like to try addressing a few things. doxygen has a bit of an issue in that it uses itself to build its own documentation. As a result of this, the HTMLDOCS and PDFDOCS options will only pull in what is needed to allow doxygen to be built in such a way to be able to build its own documentation. Because of this, if those options are left out, then doxygen will be left in a state where it can no longer build HTML docs fully (because of the lack of graphviz) and cannot build PDF docs (because of the lack of a LaTeX distribution). Because of this, consumers of doxygen, whether they be other FreeBSD ports or just users of doxygen in general, would need to have graphviz and LaTeX installed to get all of doxygen's features. I recently had someone that wanted to build doxygen without the LaTeX dependency, though. So I think ideally, the dependencies for graphviz and LaTeX should becomes separate options, and the HTMLDOCS and PDFDOCS options should only be allowed if graphviz and LaTeX, respectively, are enabled. If I add in those options, then I believe that the options for including graphviz and LaTeX should probably be made default. For something like this, though, I would need to know how many ports would need either option enabled. If the options don't need to be defaulted, then they shouldn't need it. graphviz might not be a bad one to have defaulted, but LaTeX might. If anyone does have an opinion on this, I'd like to hear it. All in all, it basically boils down to needing to find a way to include graphviz and LaTeX in a way that doesn't cause too many problems but also allows doxygen to still have the option of building its own documentation. In a semi-related point, part of the patching being done to the port involves removing doxygen's included MD5 implementation in order to use the system's MD5 implementation instead. I've heard differing opinions on this situation. Some people say that I should just let doxygen use its own MD5 implementation. But other people say that ports should always try to use the system's implementations as opposed to embedded ones. Which is better to use in this situation? I believe that doxygen's implementation of MD5 is statically linked, but patching it as I am now, it will call from the MD5 library of the system instead. Thanks, Naram Qashat ___ 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: pkg-static error when installing php5 from ports
Hi Bryan, On Thu, Aug 14, 2014 at 7:30 AM, Bryan Drewery bdrew...@freebsd.org wrote: On 8/13/2014 9:07 PM, Neel Natu wrote: No response on freebsd-pkg@ so figured I would try my luck here. best Neel On Tue, Aug 12, 2014 at 5:57 PM, Neel Natu neeln...@gmail.com wrote: Hi, I am installing php5 from ports. It builds fine but fails with this error when installing: [/usr/ports/lang/php5]$ sudo make install === Installing for php5-5.4.31 === php5-5.4.31 depends on shared library: libpcre.so - found (/usr/local/lib/libpcre.so.3) === php5-5.4.31 depends on shared library: libxml2.so - found (/usr/local/lib/libxml2.so.2.9.1) === Checking if php5 already installed === Registering installation for php5-5.4.31 pkg-static: Invalid manifest format: could not find expected ':' *** Error code 74 Stop. make[1]: stopped in /usr/ports/lang/php5 *** Error code 1 Any clue what might be happening and how to fix? best Neel This came up in #pkgng on freenode as well. Your Pkg is probably too old. Check with 'pkg -v'. The current release is at 1.3.6 now. You're likely running 1.1. Upgrade Pkg to support the new JSON format for the manifest. Thanks, that worked! best Neel -- Regards, Bryan Drewery ___ 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 marked IGNORE
On Thu, 14 Aug 2014 08:35:07 -0700, Kevin Oberman stated: For several years I have been using evince for PDF display. It's MUCH lighter weight than Acrobat and works very well. It is poppler based and will probably pull in a LOT of Gnome stuff, so it is best if you already run Gnome, MATE, or have ports installed that have already pulled in the main Gnome2 libraries. I am not all that interested in if it is light weight or not. I need a program that can view and occasionally print PDF documents correctly. I have Acrobat installed on my Windows machine, so if I need to do any heavy duty PDF work, I just transfer the file to that machine. I just don't like to have to use the Windows machine every time I just want to view or print a PDF document located on my FreeBSD machine. I will give your suggestion a perusal. Thanks! -- Jerry signature.asc Description: PGP signature
Re: Ports marked IGNORE
Am 14.08.2014 um 20:40 schrieb Jerry: On Thu, 14 Aug 2014 08:35:07 -0700, Kevin Oberman stated: For several years I have been using evince for PDF display. It's MUCH lighter weight than Acrobat and works very well. It is poppler based and will probably pull in a LOT of Gnome stuff, so it is best if you already run Gnome, MATE, or have ports installed that have already pulled in the main Gnome2 libraries. I am not all that interested in if it is light weight or not. I need a program that can view and occasionally print PDF documents correctly. I have Acrobat installed on my Windows machine, so if I need to do any heavy duty PDF work, I just transfer the file to that machine. I just don't like to have to use the Windows machine every time I just want to view or print a PDF document located on my FreeBSD machine. I will give your suggestion a perusal. Thanks! Easy to try are graphics/xpdf and print/gv, a GTK+ (or perhaps GNOME)-related one is graphics/evince, and KDE-related ones is graphics/okular. There are also - but I haven't tried them: graphics/epdfview graphics/mupdf print/qpdfview I am oblivious to their exact options and requirements, but I'm positive that you'll figure that out. ___ 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: installing packages into a mounted system
Hello,
To close this thread: after reading and understandig how it should work,
I have found the following easy solution:
# chroot /mnt pkg-static repo /PKGDIR
Creating repository in /PKGDIR: 83%
...
Packing files for repository: 100%
# chroot /mnt mkdir -p /usr/local/etc/pkg/repos
# vim /mnt/usr/local/etc/pkg/repos/myrepo.conf
# cat /mnt/usr/local/etc/pkg/repos/myrepo.conf
FreeBSD: {
url: file:/PKGDIR,
enabled: true,
}
# chroot /mnt pkg-static -R /usr/local/etc/pkg/repos/ install autoconf-2.69
Updating repository catalogue
FreeBSD repository is up-to-date
All repositories are up-to-date
The following 5 packages will be affected (of 0 checked):
New packages to be INSTALLED:
autoconf: 2.69
indexinfo: 0.2
perl5: 5.16.3_11
m4: 1.4.17_1,1
autoconf-wrapper: 20131203
The process will require 45 MB more space
13 MB to be downloaded
Proceed with this action [y/N]: y
Fetching autoconf-2.69.txz: 100% of 529 KB
Fetching indexinfo-0.2.txz: 100% of 6 KB
Fetching perl5-5.16.3_11.txz: 100% of 12 MB
Fetching m4-1.4.17_1,1.txz: 100% of 183 KB
Fetching autoconf-wrapper-20131203.txz: 100% of 4 KB
Checking integrity... done (0 conflicting)
[1/5] Installing indexinfo-0.2: 100%
[2/5] Installing perl5-5.16.3_11: 100%
[3/5] Installing m4-1.4.17_1,1: 100%
[4/5] Installing autoconf-wrapper-20131203: 100%
[5/5] Installing autoconf-2.69: 100%
# chroot /mnt pkg-static info
autoconf-2.69 Automatically configure source code on many Un*x
platforms
autoconf-wrapper-20131203 Wrapper script for GNU autoconf
indexinfo-0.2 Utility to regenerate the GNU info page index
m4-1.4.17_1,1 GNU m4
perl5-5.16.3_11Practical Extraction and Report Language
Works fine. Thanks to the people who designed this new pkg tool.
matthias
--
Matthias Apitz | /\ ASCII Ribbon Campaign:
E-mail: g...@unixarea.de | \ / - No HTML/RTF in E-mail
WWW: http://www.unixarea.de/ | X- No proprietary attachments
phone: +49-170-4527211 | / \ - Respect for open standards
| en.wikipedia.org/wiki/ASCII_Ribbon_Campaign
___
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: [Patch] Using MACHINE_ARCH identifiers in pkg
On 2014-08-14 17:35, Nathan Whitehorn wrote: On 08/14/14 08:02, Bryan Drewery wrote: On 5/28/2014 11:54 AM, Nathan Whitehorn wrote: The current/previous values are also kept so that the patched pkg can install a package marked either with an x86:64 or amd64-type architecture ID (symlinks will be needed for a little bit on the package server to allow both clients to work). Limited testing suggests it works well -- I can fetch and install packages fine. More testing would be great. Symlinks are now setup to make testing of this easier. I'll let Bapt signoff on this patch officially and its timeframe. It seems reasonable to me. The use of 'x86' almost caused a regression recently due to its ambiguity. Cheers, Bryan Thanks Bryan! If anyone is interested in testing the adapted pkg, there is a patch that can be applied to ports at http://people.freebsd.org/~nwhitehorn/pkg-new-abi.diff. It tries to make this transition as painless as possible by doing the following things: 1. Have pkg use e.g. FreeBSD:11:amd64 instead of freebsd:11:x86:64 as an ABI string. 2. Maintain the freebsd:11:x86:64-type strings as the altabi config variable. 3. pkg will install packages where the architecture ID matches either the ABI or ALTABI value, which means that new pkg can install packages made with the older version. 4. Patches the ports-mgmt/pkg Makefile so that the package for pkg itself is given a freebsd:11:x86:64-type architecture. This prevents pkg from choking on an update to itself and should, with the symlinks discussed above, make the transition painless and transparent. Especially point (4) I'd appreciate testing on if anyone is generating private package repositories. -Nathan Hi Nathan, Thanks for the patch, but there is a possible chicken - egg issue. I removed old pkg packages from the last build and running a new build so pkg was build with the patch. The first client complains about wrong architecture and there was no way to reinstall pkg (even not with force) Quick solution was to distribute pkg-static to the client and reinstall pkg with the new pkg-static. After the upgrade everything is running as usual ;) Are there better upgrade paths then my quick workaround ? Output after pd build was finished on the first client. # pkg update -f Updating repository catalogue Fetching meta.txz: 100% of 584 B Fetching digests.txz: 100% of 43 kB Fetching packagesite.txz: 100% of 138 kB Adding new entries: 34% pkg: wrong architecture: FreeBSD:8:amd64 instead of freebsd:8:x86:64 pkg: repository str contains packages with wrong ABI: FreeBSD:8:amd64 Adding new entries: 100% pkg: Unable to update repository str Update with help of the patched pkg # ~/pkg-static update -f Updating repository catalogue pkg-static: Repository str has a wrong packagesite, need to re-create database Fetching meta.txz: 100% of 584 B Fetching digests.txz: 100% of 43 kB Fetching packagesite.txz: 100% of 138 kB Adding new entries: 100% Incremental update completed, 500 packages processed: 0 packages updated, 0 removed and 500 added. -- olli ___ 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: [Patch] Using MACHINE_ARCH identifiers in pkg
On 8/14/2014 2:38 PM, olli hauer wrote: On 2014-08-14 17:35, Nathan Whitehorn wrote: On 08/14/14 08:02, Bryan Drewery wrote: On 5/28/2014 11:54 AM, Nathan Whitehorn wrote: The current/previous values are also kept so that the patched pkg can install a package marked either with an x86:64 or amd64-type architecture ID (symlinks will be needed for a little bit on the package server to allow both clients to work). Limited testing suggests it works well -- I can fetch and install packages fine. More testing would be great. Symlinks are now setup to make testing of this easier. I'll let Bapt signoff on this patch officially and its timeframe. It seems reasonable to me. The use of 'x86' almost caused a regression recently due to its ambiguity. Cheers, Bryan Thanks Bryan! If anyone is interested in testing the adapted pkg, there is a patch that can be applied to ports at http://people.freebsd.org/~nwhitehorn/pkg-new-abi.diff. It tries to make this transition as painless as possible by doing the following things: 1. Have pkg use e.g. FreeBSD:11:amd64 instead of freebsd:11:x86:64 as an ABI string. 2. Maintain the freebsd:11:x86:64-type strings as the altabi config variable. 3. pkg will install packages where the architecture ID matches either the ABI or ALTABI value, which means that new pkg can install packages made with the older version. 4. Patches the ports-mgmt/pkg Makefile so that the package for pkg itself is given a freebsd:11:x86:64-type architecture. This prevents pkg from choking on an update to itself and should, with the symlinks discussed above, make the transition painless and transparent. Especially point (4) I'd appreciate testing on if anyone is generating private package repositories. -Nathan Hi Nathan, Thanks for the patch, but there is a possible chicken - egg issue. I removed old pkg packages from the last build and running a new build so pkg was build with the patch. The first client complains about wrong architecture and there was no way to reinstall pkg (even not with force) Quick solution was to distribute pkg-static to the client and reinstall pkg with the new pkg-static. After the upgrade everything is running as usual ;) Are there better upgrade paths then my quick workaround ? Output after pd build was finished on the first client. # pkg update -f Updating repository catalogue Fetching meta.txz: 100% of 584 B Fetching digests.txz: 100% of 43 kB Fetching packagesite.txz: 100% of 138 kB Adding new entries: 34% pkg: wrong architecture: FreeBSD:8:amd64 instead of freebsd:8:x86:64 pkg: repository str contains packages with wrong ABI: FreeBSD:8:amd64 Adding new entries: 100% pkg: Unable to update repository str Update with help of the patched pkg # ~/pkg-static update -f Updating repository catalogue pkg-static: Repository str has a wrong packagesite, need to re-create database Fetching meta.txz: 100% of 584 B Fetching digests.txz: 100% of 43 kB Fetching packagesite.txz: 100% of 138 kB Adding new entries: 100% Incremental update completed, 500 packages processed: 0 packages updated, 0 removed and 500 added. -- olli Something I've mentioned to Bapt a few times is that pkg needs a way to have a list of accepted ABI strings. Then we could add both the old and the new style as accepted (internally) so that old and new repositories will continue to work. -- Regards, Bryan Drewery signature.asc Description: OpenPGP digital signature
Re: [Patch] Using MACHINE_ARCH identifiers in pkg
On 2014-08-14 21:42, Bryan Drewery wrote: On 8/14/2014 2:38 PM, olli hauer wrote: On 2014-08-14 17:35, Nathan Whitehorn wrote: ... Something I've mentioned to Bapt a few times is that pkg needs a way to have a list of accepted ABI strings. Then we could add both the old and the new style as accepted (internally) so that old and new repositories will continue to work. Ups, rollback is not possible after the client database was updated. Even by rollback and rebuild the package metadata the following error pops up. ~/pkg-static.old_ABI update -f Updating repository catalogue pkg-static: Repository str has a wrong packagesite, need to re-create database Fetching meta.txz: 100% of 584 B Fetching digests.txz: 100% of 43 kB Fetching packagesite.txz: 100% of 138 kB Adding new entries: 34% pkg-static: wrong architecture: FreeBSD:8:amd64 instead of freebsd:8:x86:64 pkg-static: repository str contains packages with wrong ABI: FreeBSD:8:amd64 Adding new entries: 100% pkg-static: Unable to update repository str Roll back on the client # ~/bin/pkg-static backup -r /var/backups/pkgng.db Roll back on the build host: - remove all packages that where created meanwhile with the patched pkg including pkg. - reinstall unpatched pkg on the build host - start a new build By doing a manual cleanup I also found that packages containing the old ABI are not removed. # ls -ltr -rw-r--r-- 2 root wheel 2592992 Aug 14 21:10 openssl-1.0.1_15.txz -rw-r--r-- 2 root wheel 1963944 Aug 14 21:11 subversion-1.8.10_1.txz # ls -l openssl* -rw-r--r-- 3 root wheel 2593488 Aug 11 17:31 openssl-1.0.1_14.txz -rw-r--r-- 2 root wheel 2592992 Aug 14 21:10 openssl-1.0.1_15.txz So the patch has more side affects ... Anyway I'm happy to test new patches to get rid of the old ABI string ;) -- olli ___ 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: net-im/skype-[devel] won't connect
On Thursday 14 August 2014 16:53:21 Artyom Mirgorodskiy wrote: The problem not in the skype. The problem in the linux pulse audio libs. I try to setup pulse audio server on freebsd and configure to tcp/ip protocol - works fine. But linux pulse client with the same config don't work (I tried simple console utils). I don't know how to trace problem. But possible pulse audio libs require some missing lib (open by dlopen) On Wednesday 13 August 2014 22:09:22 Vassilis Laganakos wrote: Hi, On Wed, Aug 13, 2014 at 10:47:25AM -0500, Scot Hetzel wrote: On Wed, Aug 13, 2014 at 10:38 AM, Kenta S. ken...@hush.com wrote: Hello. This afternoon when I try to sign onto Skype, I get: Periodic UIC Update Failed I haven't updated ports recently. Does anyone have an idea? I heard Skype was closing down old versions. I had received the following e-mail from Skype a few days ago: On Fri, Aug 8, 2014 at 7:53 PM, Skype norep...@emails.skype.com wrote: Your Skype for Linux version is being retired. Update today. » Can't see this email properly? Forgotten your password? Your Skype for Linux version is being retired. Update today. Dear swhetzel, We are now retiring older versions of Skype and it appears that at some point you signed into Skype with one of these. To continue signing into Skype on Linux you'll need to download the latest version. The new version comes with improved performance, the latest features and security updates, so you'll get the best possible Skype experience. If you're on the latest version of Skype, the above will not apply. Update now at http://www.skype.com/download. Someone will need to update the Skype port to the latest Linux version and see if it works on our current version of Linux emulation. I've read in various places (and tested myself with a couple of version on Linux) that any version before skype 4.3.0.37 will not connect. The skype port at: https://github.com/vassilisl/freebsd-ports/tree/master/net-im/skype4 will connect (if you use the f20 ports https://github.com/vassilisl/freebsd-linux_base-f20 ;) ) but it doesn't have sound working. Both xmj and I are working on getting that version of Skype on c6 and f20 linux emulation bases respectivelly, which basically means get it to talk to pulseaudio. If anyone has experience with that, please shout! :) Regards, Vassilis The trick from FreeBSD Forum works for me: http://forums.freebsd.org/viewtopic.php?f=22t=44800start=75 -- ajtiM http://www.redbubble.com/people/lumiwa ___ 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: [Patch] Using MACHINE_ARCH identifiers in pkg
On 08/14/14 12:38, olli hauer wrote: On 2014-08-14 17:35, Nathan Whitehorn wrote: On 08/14/14 08:02, Bryan Drewery wrote: On 5/28/2014 11:54 AM, Nathan Whitehorn wrote: The current/previous values are also kept so that the patched pkg can install a package marked either with an x86:64 or amd64-type architecture ID (symlinks will be needed for a little bit on the package server to allow both clients to work). Limited testing suggests it works well -- I can fetch and install packages fine. More testing would be great. Symlinks are now setup to make testing of this easier. I'll let Bapt signoff on this patch officially and its timeframe. It seems reasonable to me. The use of 'x86' almost caused a regression recently due to its ambiguity. Cheers, Bryan Thanks Bryan! If anyone is interested in testing the adapted pkg, there is a patch that can be applied to ports at http://people.freebsd.org/~nwhitehorn/pkg-new-abi.diff. It tries to make this transition as painless as possible by doing the following things: 1. Have pkg use e.g. FreeBSD:11:amd64 instead of freebsd:11:x86:64 as an ABI string. 2. Maintain the freebsd:11:x86:64-type strings as the altabi config variable. 3. pkg will install packages where the architecture ID matches either the ABI or ALTABI value, which means that new pkg can install packages made with the older version. 4. Patches the ports-mgmt/pkg Makefile so that the package for pkg itself is given a freebsd:11:x86:64-type architecture. This prevents pkg from choking on an update to itself and should, with the symlinks discussed above, make the transition painless and transparent. Especially point (4) I'd appreciate testing on if anyone is generating private package repositories. -Nathan Hi Nathan, Thanks for the patch, but there is a possible chicken - egg issue. I removed old pkg packages from the last build and running a new build so pkg was build with the patch. The first client complains about wrong architecture and there was no way to reinstall pkg (even not with force) Quick solution was to distribute pkg-static to the client and reinstall pkg with the new pkg-static. After the upgrade everything is running as usual ;) Are there better upgrade paths then my quick workaround ? Output after pd build was finished on the first client. # pkg update -f Updating repository catalogue Fetching meta.txz: 100% of 584 B Fetching digests.txz: 100% of 43 kB Fetching packagesite.txz: 100% of 138 kB Adding new entries: 34% pkg: wrong architecture: FreeBSD:8:amd64 instead of freebsd:8:x86:64 pkg: repository str contains packages with wrong ABI: FreeBSD:8:amd64 Adding new entries: 100% pkg: Unable to update repository str Update with help of the patched pkg # ~/pkg-static update -f Updating repository catalogue pkg-static: Repository str has a wrong packagesite, need to re-create database Fetching meta.txz: 100% of 584 B Fetching digests.txz: 100% of 43 kB Fetching packagesite.txz: 100% of 138 kB Adding new entries: 100% Incremental update completed, 500 packages processed: 0 packages updated, 0 removed and 500 added. -- olli Hm, that's weird. The patch is specifically designed to fix this. Could you run pkg info -F pkg.txz on the new pkg package that you can't install? -Nathan ___ 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: Cannot solve problem using SAT solver
Hello, Trying to upgrade a machine with `pkg upgrade', it displays these messages: pkg: Cannot solve problem using SAT solver: cannot install package ecs~science/ecs, remove it from request [Y/n]: Y pkg: Cannot solve problem using SAT solver: cannot install package apache22~www/apache22, remove it from request [Y/n]: Y cannot install package mod_php5~www/mod_php5, remove it from request [Y/n]: Y This is pkg 1.3.6. Is it possible to upgrade these packages with pkg, or do we need to use the ports? Regards, -- Th. Thomas. ___ 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: [Patch] Using MACHINE_ARCH identifiers in pkg
... Something I've mentioned to Bapt a few times is that pkg needs a way to have a list of accepted ABI strings. Then we could add both the old and the new style as accepted (internally) so that old and new repositories will continue to work. Yes, this would help. I tried as workaround to rebuild the repo catalogs with the un-patched pkg tool but get on the next system the same complain about changed ABI. I will roll back to the test system, so new patches can be tested ... -- olli ___ 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: [Patch] Using MACHINE_ARCH identifiers in pkg
On 08/14/14 12:42, Bryan Drewery wrote: On 8/14/2014 2:38 PM, olli hauer wrote: On 2014-08-14 17:35, Nathan Whitehorn wrote: On 08/14/14 08:02, Bryan Drewery wrote: On 5/28/2014 11:54 AM, Nathan Whitehorn wrote: The current/previous values are also kept so that the patched pkg can install a package marked either with an x86:64 or amd64-type architecture ID (symlinks will be needed for a little bit on the package server to allow both clients to work). Limited testing suggests it works well -- I can fetch and install packages fine. More testing would be great. Symlinks are now setup to make testing of this easier. I'll let Bapt signoff on this patch officially and its timeframe. It seems reasonable to me. The use of 'x86' almost caused a regression recently due to its ambiguity. Cheers, Bryan Thanks Bryan! If anyone is interested in testing the adapted pkg, there is a patch that can be applied to ports at http://people.freebsd.org/~nwhitehorn/pkg-new-abi.diff. It tries to make this transition as painless as possible by doing the following things: 1. Have pkg use e.g. FreeBSD:11:amd64 instead of freebsd:11:x86:64 as an ABI string. 2. Maintain the freebsd:11:x86:64-type strings as the altabi config variable. 3. pkg will install packages where the architecture ID matches either the ABI or ALTABI value, which means that new pkg can install packages made with the older version. 4. Patches the ports-mgmt/pkg Makefile so that the package for pkg itself is given a freebsd:11:x86:64-type architecture. This prevents pkg from choking on an update to itself and should, with the symlinks discussed above, make the transition painless and transparent. Especially point (4) I'd appreciate testing on if anyone is generating private package repositories. -Nathan Hi Nathan, Thanks for the patch, but there is a possible chicken - egg issue. I removed old pkg packages from the last build and running a new build so pkg was build with the patch. The first client complains about wrong architecture and there was no way to reinstall pkg (even not with force) Quick solution was to distribute pkg-static to the client and reinstall pkg with the new pkg-static. After the upgrade everything is running as usual ;) Are there better upgrade paths then my quick workaround ? Output after pd build was finished on the first client. # pkg update -f Updating repository catalogue Fetching meta.txz: 100% of 584 B Fetching digests.txz: 100% of 43 kB Fetching packagesite.txz: 100% of 138 kB Adding new entries: 34% pkg: wrong architecture: FreeBSD:8:amd64 instead of freebsd:8:x86:64 pkg: repository str contains packages with wrong ABI: FreeBSD:8:amd64 Adding new entries: 100% pkg: Unable to update repository str Update with help of the patched pkg # ~/pkg-static update -f Updating repository catalogue pkg-static: Repository str has a wrong packagesite, need to re-create database Fetching meta.txz: 100% of 584 B Fetching digests.txz: 100% of 43 kB Fetching packagesite.txz: 100% of 138 kB Adding new entries: 100% Incremental update completed, 500 packages processed: 0 packages updated, 0 removed and 500 added. -- olli Something I've mentioned to Bapt a few times is that pkg needs a way to have a list of accepted ABI strings. Then we could add both the old and the new style as accepted (internally) so that old and new repositories will continue to work. That's one thing this patch does internally, so that the patched version accepts either. Of course, it can't alter previous versions of pkg... -Nathan ___ 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] 364903: 2x leftovers, 2x ???
- Use USES=python - Build ID: 20140815030205-14652 Job owner: sunp...@freebsd.org Buildtime: 41 minutes Enddate: Fri, 15 Aug 2014 03:42:38 GMT Revision: 364903 Repository: https://svnweb.freebsd.org/ports?view=revisionrevision=364903 - Port:graphics/py-ming Buildgroup: 8.4-QAT/amd64 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~sunp...@freebsd.org/20140815030205-14652-396634/py27-ming-0.4.5_1.log Buildgroup: 8.4-QAT/i386 Buildstatus: LEFTOVERS Log: https://qat.redports.org//~sunp...@freebsd.org/20140815030205-14652-396635/py27-ming-0.4.5_1.log Buildgroup: 9.2-QAT/amd64 Buildstatus: ??? Log: https://qat.redports.org//~sunp...@freebsd.org/20140815030205-14652-396636/py27-ming-0.4.5_1.log Buildgroup: 9.2-QAT/i386 Buildstatus: ??? Log: https://qat.redports.org//~sunp...@freebsd.org/20140815030205-14652-396637/py27-ming-0.4.5_1.log -- Buildarchive URL: https://qat.redports.org/buildarchive/20140815030205-14652 redports https://qat.redports.org/ ___ 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
