Fwd: keysearch fails
Hello kuriy...@freebsd.org, There seems to be a bug in GnuPG 2.1.x dirmngr which let it crash; the attached diff at least solves the crash, even if there are other errors while searching for pub keys :-( matthias - Forwarded message from Matthias Apitz - Date: Wed, 23 Dec 2015 09:23:12 +0100 From: Matthias Apitz To: gnupg-us...@gnupg.org Subject: keysearch fails Hello, I can not manage to get a keysearch via dirmngr to work; when I use: $ gpg2 --keyserver pool.sks-keyservers.net --debug 1024 --search x...@freebsd.org gpg: reading options from '/home/guru/.gnupg/gpg.conf' gpg: enabled debug flags: ipc gpg: DBG: chan_3 <- # Home: /home/guru/.gnupg gpg: DBG: chan_3 <- # Config: /home/guru/.gnupg/dirmngr.conf gpg: DBG: chan_3 <- OK Dirmngr 2.1.6 at your service gpg: DBG: connection to the dirmngr established gpg: DBG: chan_3 -> KEYSERVER --clear hkp://pool.sks-keyservers.net gpg: DBG: chan_3 <- OK gpg: DBG: chan_3 -> KS_SEARCH -- x...@freebsd.org gpg: DBG: chan_3 <- [eof] gpg: error searching keyserver: End of file gpg: búsqueda del servidor de claves fallida: End of file gpg: DBG: chan_3 -> BYE gpg: secmem usage: 0/32768 bytes in 0 blocks In /var/log/message I see: Dec 23 09:15:09 c720-r285885-amd64 kernel: pid 2809 (dirmngr), uid 1001: exited on signal 6 which perhaps is normal (soemhow the spawned proc must be killed); but a TCPDUMP only shows a lot of PTR requests, see below. No real traffic is to be seen to no server. What I do miss here? matthias 09:15:57.465887 IP 10.42.0.152.26961 > 10.42.0.1.53: 57200+ A? pool.sks-keyservers.net. (41) 09:15:57.698231 IP 10.42.0.1.53 > 10.42.0.152.26961: 57200 10/0/0 A 176.9.51.79, A 193.224.163.43, A 207.237.164.231, A 193.17.17.6, A 85.93.13.183, A 104.236.44.212, A 46.229.47.139, A 223.252.21.101, A 192.71.151.126, A 144.76.120.109 (201) 09:15:57.698443 IP 10.42.0.152.15292 > 10.42.0.1.53: 44337+ ? pool.sks-keyservers.net. (41) 09:15:58.136982 IP 10.42.0.1.53 > 10.42.0.152.15292: 44337 10/0/0 2604:a880:800:10::60d:b001, 2a03:4000:6:202e::1, 2a01:7a0:1::6, 2001:470:1f09:1d75::80, 2a01:4f8:a0:4024::2:0, 2a01:4f8:150:7142::2, 2001:41d0:2:a8b4::10, 2a02:168:4a01::37, 2604:a880:800:10::688:e001, 2001:6f8:124e::1 (321) 09:15:58.138270 IP 10.42.0.152.57903 > 10.42.0.1.53: 3651+ PTR? 212.44.236.104.in-addr.arpa. (45) 09:15:58.139749 IP 10.42.0.1.53 > 10.42.0.152.57903: 3651 1/0/0 PTR openpgp.us. (69) 09:15:58.140405 IP 10.42.0.152.49791 > 10.42.0.1.53: 29976+ PTR? 126.151.71.192.in-addr.arpa. (45) 09:15:58.142479 IP 10.42.0.1.53 > 10.42.0.152.49791: 29976 1/0/0 PTR mimir.alderwick.co.uk. (80) 09:15:58.142854 IP 10.42.0.152.20861 > 10.42.0.1.53: 61059+ PTR? 101.21.252.223.in-addr.arpa. (45) 09:15:58.144671 IP 10.42.0.1.53 > 10.42.0.152.20861: 61059 1/0/0 PTR svcs4.riverwillow.net.au. (83) 09:15:58.145031 IP 10.42.0.152.51574 > 10.42.0.1.53: 21456+ PTR? 139.47.229.46.in-addr.arpa. (44) 09:15:58.146670 IP 10.42.0.1.53 > 10.42.0.152.51574: 21456 1/0/0 PTR jarvis.alpha-labs.net. (79) 09:15:58.147016 IP 10.42.0.152.24483 > 10.42.0.1.53: 11392+ PTR? 79.51.9.176.in-addr.arpa. (42) 09:15:58.149302 IP 10.42.0.1.53 > 10.42.0.152.24483: 11392 1/0/0 PTR alita.karotte.org. (73) 09:15:58.149639 IP 10.42.0.152.45716 > 10.42.0.1.53: 51515+ PTR? 183.13.93.85.in-addr.arpa. (43) 09:15:58.150581 IP 10.42.0.1.53 > 10.42.0.152.45716: 51515 1/0/0 PTR host10.slyinvestment.com. (81) 09:15:58.151058 IP 10.42.0.152.31608 > 10.42.0.1.53: 34134+ PTR? 6.17.17.193.in-addr.arpa. (42) 09:15:58.153963 IP 10.42.0.1.53 > 10.42.0.152.31608: 34134 1/0/0 PTR key.ip6.li. (66) 09:15:58.154314 IP 10.42.0.152.37867 > 10.42.0.1.53: 56496+ PTR? 231.164.237.207.in-addr.arpa. (46) 09:15:58.156621 IP 10.42.0.1.53 > 10.42.0.152.37867: 56496 1/0/0 PTR keys.sflc.info. (74) 09:15:58.156959 IP 10.42.0.152.20412 > 10.42.0.1.53: 34648+ PTR? 43.163.224.193.in-addr.arpa. (45) 09:15:58.158943 IP 10.42.0.1.53 > 10.42.0.152.20412: 34648 1/0/0 PTR hufu.ki.iif.hu. (73) 09:15:58.159277 IP 10.42.0.152.46457 > 10.42.0.1.53: 32569+ PTR? 109.120.76.144.in-addr.arpa. (45) 09:15:58.161678 IP 10.42.0.1.53 > 10.42.0.152.46457: 32569 1/0/0 PTR encrypt.to. (69) 09:15:58.162290 IP 10.42.0.152.58716 > 10.42.0.1.53: 61479+ PTR? 0.0.0.0.2.0.0.0.0.0.0.0.0.0.0.0.4.2.0.4.0.a.0.0.8.f.4.0.1.0.a.2.ip6.arpa. (90) 09:15:58.163688 IP 10.42.0.1.53 > 10.42.0.152.58716: 61479 1/0/0 PTR a.keyserver.pki.scientia.net. (132) 09:15:58.164128 IP 10.42.0.152.32231 > 10.42.0.1.53: 26254+ PTR? 1.0.0.e.8.8.6.0.0.0.0.0.0.0.0.0.0.1.0.0.0.0.8.0.0.8.8.a.4.0.6.2.ip6.arpa. (90) 09:15:58.166679 IP 10.42.0.1.53 > 10.42.0.152.32231: 26254 0/0/0 (90) 09:15:58.167037 IP 10.42.0.152.15342 > 10.42.0.1.53: 14504+ PTR? 7.3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.1.0.a.4.8.6.1.0.2.0.a.2.ip6.arpa. (90) 09:15:58.168514 IP 10.42.0.1.53 > 10.42.0.152.15342: 14504 1/0/0 PTR pgpkeys.urown.net. (121) 09:15:58.168872 IP 10.42.0.152.49875 > 10.42.0.1.53: 39926+ PTR? 0.1
java/wildfly discussion
Hello all. Seems that I've created too many ports for wildfly, let's discuss sanation :) https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205490 -- Regards, Alexander Yerenkow ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: java/wildfly discussion
hi all, i'm using also the old versions because of stability of these, also if not supported. problem is that the new versions are different and it's impossible to change all few month's the version (and reconfigure everything), i have also running versions 4.x and 5.x. also if compliance is written this is not true (just an example: small changes in security can bring a project to fail very fast, means the dependencies of the jar files which are used to compile) at the moment the versions are 9.0.2 Final 15/10 9.0.1 Final 15/07/23 9.0.0 Final 15/07/02 8.2.1 Final 15/07 8.2.0 Final 14/11 8.1.0 Final 14/05 Start was 2013 my question is it hurting to keep them in the svn ? better would be a subdirectory for ever major release and subdirectories for the minor releases like /usr/ports/java/ wildfly9/ wildfly9-currentfor the very optimistic once's wildfly9.0.1 wildfly9.0.2 wildfly8/ i also would keep it about 3 years than a deprecation and later deletion can be done… and really I’m working with jboss 2000 / and then with wildfly and it never worked to upgrade without problems en recompilation/remerging/reconfiguriing of the running apps i have seen there are packages for upgrade from 9.0.1 to 9.0.2 for example, but i’m not sure if would be easy to integrate this into the ports system ?! this would be another chance to resolve too much ports (but also with the same problems apps running on the app server will fail… ) br horst > On 23 Dec 2015, at 12:09, Alexander Yerenkow wrote: > > Hello all. > Seems that I've created too many ports for wildfly, let's discuss sanation > :) > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=205490 > > > -- > Regards, > Alexander Yerenkow > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" smime.p7s Description: S/MIME cryptographic signature
USES=fortran can't mix with the libraries requiring /lib/libgcc_s.so.1 from the base
I found that ports with USES=fortran can't mix with anything in C++ compiled with the base clang++, because USES=fortran forces the current gcc that links with its /usr/local/lib/libgcc_s.so.1 Getting this particular error from the python process, because one python module has USES=fortran, and another has C++ in it: ImportError: /lib/libgcc_s.so.1: version GCC_4.6.0 required by /usr/local/lib/gcc48/libgfortran.so.3 not found What is the general solution for this problem? Is there a non-gcc version of fortran? One thing is when gcc is required because clang can't compile something, and another things is when fortran language requires it. The latter is here to stay. Can there be the separate fortran from gcc that is build with clang? Or can we switch /usr/ports/lang/gccNN to be always built with the base clang? I know this is certainly possible. Yuri ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Failed upgrade graphics/ImageMagick: /usr/bin/ld: skipping incompatible /usr/lib32/...
Today's daily stable/10 laptop update was from: FreeBSD g1-252.catwhisker.org 10.2-STABLE FreeBSD 10.2-STABLE #235 r292590M/292594:1002504: Tue Dec 22 04:31:23 PST 2015 r...@g1-252.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY amd64 to: FreeBSD g1-252.catwhisker.org 10.2-STABLE FreeBSD 10.2-STABLE #236 r292656M/292657:1002504: Wed Dec 23 04:20:06 PST 2015 r...@g1-252.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY amd64 After a successful reboot, I then (as is my custom) invoked portmaster to update the installed ports on it; the following were selected: ===>>> The following actions will be taken if you choose to proceed: Upgrade rpm2cpio-1.4 to rpm2cpio-1.4_1 Upgrade ImageMagick-6.9.2.8_1,1 to ImageMagick-6.9.2.10,1 Upgrade librsvg2-2.40.10 to librsvg2-2.40.12 Upgrade libXi-1.7.5,1 to libXi-1.7.6,1 Upgrade openjdk8-8.66.17 to openjdk8-8.66.17_1 /usr/ports had been updated to 404287 (on ports/head). During the initial pass, the ImageMagick update failed; I proceeded with the remianing 3 (which succeeeded), then re-tried ImageMagick, which failed again in the same way: ... ===> Building for ImageMagick-6.9.2.10,1 gmake[2]: Entering directory '/common/ports/graphics/ImageMagick/work/ImageMagick-6.9.2-10' gmake all-am gmake[3]: Entering directory '/common/ports/graphics/ImageMagick/work/ImageMagick-6.9.2-10' cp -f magick/ImageMagick.pc magick/ImageMagick-6.pc cp -f magick/MagickCore.pc magick/MagickCore-6.pc cp -f wand/MagickWand.pc wand/MagickWand-6.pc cp -f wand/Wand.pc wand/Wand-6.pc cp -f Magick++/lib/Magick++.pc Magick++/lib/Magick++-6.pc cp -f Magick++/lib/ImageMagick++.pc Magick++/lib/ImageMagick++-6.pc GEN PerlMagick/quantum/Q16HDRI.xs GEN PerlMagick/quantum/Q16HDRI.pm CC coders/coders_aai_la-aai.lo CC magick/magick_libMagickCore_6_la-animate.lo ... CC utilities/montage.o CC utilities/stream.o CCLD magick/libMagickCore-6.la /usr/bin/ld: skipping incompatible /usr/lib32/liblzma.so when searching for -llzma /usr/bin/ld: skipping incompatible /usr/lib32/liblzma.a when searching for -llzma /usr/bin/ld: skipping incompatible /usr/lib32/libbz2.so when searching for -lbz2 /usr/bin/ld: skipping incompatible /usr/lib32/libbz2.a when searching for -lbz2 /usr/bin/ld: skipping incompatible /usr/lib32/libz.so when searching for -lz /usr/bin/ld: skipping incompatible /usr/lib32/libz.a when searching for -lz /usr/bin/ld: skipping incompatible /usr/lib32/libm.so when searching for -lm /usr/bin/ld: skipping incompatible /usr/lib32/libm.a when searching for -lm /usr/bin/ld: skipping incompatible /usr/lib32/libpthread.so when searching for -lpthread /usr/bin/ld: skipping incompatible /usr/lib32/libpthread.a when searching for -lpthread /usr/bin/ld: skipping incompatible /usr/lib32/libgcc.a when searching for -lgcc /usr/bin/ld: skipping incompatible /usr/lib32/libgcc_s.so when searching for -lgcc_s /usr/bin/ld: skipping incompatible /usr/lib32/libpthread.so when searching for -lpthread /usr/bin/ld: skipping incompatible /usr/lib32/libpthread.a when searching for -lpthread /usr/bin/ld: skipping incompatible /usr/lib32/libc.so.7 when searching for /usr/lib32/libc.so.7 /usr/bin/ld: cannot find /usr/lib32/libc.so.7 cc: error: linker command failed with exit code 1 (use -v to see invocation) Makefile:6617: recipe for target 'magick/libMagickCore-6.la' failed gmake[3]: *** [magick/libMagickCore-6.la] Error 1 gmake[3]: *** Waiting for unfinished jobs gmake[3]: Leaving directory '/common/ports/graphics/ImageMagick/work/ImageMagick-6.9.2-10' Makefile:5194: recipe for target 'all' failed gmake[2]: *** [all] Error 2 gmake[2]: Leaving directory '/common/ports/graphics/ImageMagick/work/ImageMagick-6.9.2-10' ===> Compilation failed unexpectedly. Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to the maintainer. *** Error code 1 Stop. make[1]: stopped in /common/ports/graphics/ImageMagick *** Error code 1 Stop. make: stopped in /common/ports/graphics/ImageMagick ===>>> make build failed for graphics/ImageMagick ===>>> Aborting update ===>>> You can restart from the point of failure with this command line: portmaster graphics/ImageMagick Script done on Wed Dec 23 04:40:36 2015 As I am not attempting to cross-build -- this is a native amd64 environment; no jails; no virtualization -- and building "for local consumption," I'm not at all clear why the port was looking at 32-bit libraries in the first place ... but I freely admit that I've never had occasion to examine that in detail before, so don't take that as anything more than an admission of ignorance. The change to the port itself appears to be quite minor: g1-252(11.0-C)[12] dirs /usr/ports/graphics/ImageMagick g1-252(11.0-C)[13] svn log Makefile |head -3 r404265 | kwm | 2015-12-22 12:04:50 -0800 (Tue, 22 Dec 2015) | 2 lines g1-2
Reporting fixes so that vuxml can be updated
Hi, "pkg audit" on my system returns the following CVE's for ffmpeg. I have noted in the list below that http://www.ffmpeg.org/security.html claims these CVE's were fixed in the ffmpeg version noted. Is this the correct place/list to report updates to that vuxml can be updated? I know there was a discussion about ports and security reporting and updating but I don't remember an outcome. Happy holidays, --mikej handbrake-0.10.2_2 is vulnerable: ffmpeg -- multiple vulnerabilities CVE: CVE-2015-6826 < Fixed in 2.7.2 CVE: CVE-2015-6825 < Fixed in 2.7.2 CVE: CVE-2015-6824 < Fixed in 2.7.2 CVE: CVE-2015-6823 < Fixed in 2.7.2 CVE: CVE-2015-6822 < Fixed in 2.7.2 CVE: CVE-2015-6821 < Fixed in 2.7.2 CVE: CVE-2015-6820 < Fixed in 2.7.2 CVE: CVE-2015-6819 < Fixed in 2.7.2 CVE: CVE-2015-6818 < Fixed in 2.7.2 WWW: https://vuxml.FreeBSD.org/freebsd/3d950687-b4c9-4a86-8478-c56743547af8.html handbrake-0.10.2_2 is vulnerable: ffmpeg -- use-after-free CVE: CVE-2015-3417 < Fixed in 2.5.2 WWW: https://vuxml.FreeBSD.org/freebsd/da434a78-e342-4d9a-87e2-7497e5f117ba.html handbrake-0.10.2_2 is vulnerable: ffmpeg -- multiple vulnerabilities CVE: CVE-2015-8365 < Fixed in 2.4.12 CVE: CVE-2015-8364 < Fixed in 2.4.12 CVE: CVE-2015-8363 < Fixed in 2.4.12 CVE: CVE-2015-8219 < Fixed in 2.4.12 CVE: CVE-2015-8218 < Fixed in 2.8.2 CVE: CVE-2015-8217 < Fixed in 2.8.2 CVE: CVE-2015-8216 < Fixed in 2.8.2 CVE: CVE-2015-6761 < Fixed in 2.8.2 WWW: https://vuxml.FreeBSD.org/freebsd/b0da85af-21a3-4c15-a137-fe9e4bc86002.html handbrake-0.10.2_2 is vulnerable: ffmpeg -- out-of-bounds array access CVE: CVE-2015-3395 < Fixed in 2.7 WWW: https://vuxml.FreeBSD.org/freebsd/80c66af0-d1c5-449e-bd31-63b12525ff88.html ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: USES=fortran can't mix with the libraries requiring /lib/libgcc_s.so.1 from the base
On Wed, Dec 23, 2015 at 04:35:29AM -0800, Yuri wrote: > I found that ports with USES=fortran can't mix with anything in C++ > compiled with the base clang++, because USES=fortran forces the current > gcc that links with its /usr/local/lib/libgcc_s.so.1 It's a well known bug. The long term fix would be bringing in quad math support which is what (gcc) fortran libs are looking for and we do not supply currently. Start here https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196491 I tried very hard to make gnuradio compiled only with clang for the 'C' parts but we were forced to use gcc. > Getting this particular error from the python process, because one > python module has USES=fortran, and another has C++ in it: > ImportError: /lib/libgcc_s.so.1: version GCC_4.6.0 required by > /usr/local/lib/gcc48/libgfortran.so.3 not found Yep. > > What is the general solution for this problem? Is there a non-gcc > version of fortran? No there is currently no clang version of Fortran. 'flang' was a SOC project to bring in clang support for fortran but it is moribund. The clang guys are the ones you should bug. In any case, the Fortran spec now requires quad math support so that would have to be provided as well. > > One thing is when gcc is required because clang can't compile something, > and another things is when fortran language requires it. The latter is > here to stay. > > Can there be the separate fortran from gcc that is build with clang? Or > can we switch /usr/ports/lang/gccNN to be always built with the base > clang? I know this is certainly possible. No. The core problem is due to our version of libgcc not having quadmath support. > > Yuri Diane -- - d...@freebsd.org d...@db.net http://www.db.net/~db ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
xfe 1.40.1 - PCBSD 10.2 - clipboard problem
Hello, I've just installed XFE on the last version of PCBSD and there is a problem of clipboard - copy/paste of text does not work in xfe/xfw. Please, fix this bug. Best regards, Peter ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: USES=fortran can't mix with the libraries requiring /lib/libgcc_s.so.1 from the base
On 12/23/2015 06:34, Diane Bruce wrote: No. The core problem is due to our version of libgcc not having quadmath support. If the separate port would have been created for gcc with only fortran in it, and it would have been compiled with clang, this would have solved this problem. Yuri ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Reporting fixes so that vuxml can be updated
Michael Jung writes: > "pkg audit" on my system returns the following CVE's for ffmpeg. I > have noted > in the list below that http://www.ffmpeg.org/security.html claims > these CVE's > were fixed in the ffmpeg version noted. > > Is this the correct place/list to report updates to that vuxml can be > updated? No updates to vuxml are needed (or appropriate). Update your ffmpeg port and you'll be fine. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: USES=fortran can't mix with the libraries requiring /lib/libgcc_s.so.1 from the base
On Wed, Dec 23, 2015 at 07:38:47AM -0800, Yuri wrote: > On 12/23/2015 06:34, Diane Bruce wrote: > > No. The core problem is due to our version of libgcc not having quadmath > > support. > > > > If the separate port would have been created for gcc with only fortran > in it, and it would have been compiled with clang, this would have > solved this problem. It is not that simple. Please read the various threads to understand why. > > Yuri > Diane -- - d...@freebsd.org d...@db.net http://www.db.net/~db ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Reporting fixes so that vuxml can be updated
On 2015-12-23 11:55, Lowell Gilbert wrote: Michael Jung writes: "pkg audit" on my system returns the following CVE's for ffmpeg. I have noted in the list below that http://www.ffmpeg.org/security.html claims these CVE's were fixed in the ffmpeg version noted. Is this the correct place/list to report updates to that vuxml can be updated? No updates to vuxml are needed (or appropriate). Update your ffmpeg port and you'll be fine. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" I neglected to state that my port is current ffmpeg-2.8.3_2,1 Realtime audio/video encoder/converter and streaming server Yet all the CVE's reported by "pkg audit" have been fixed according to the ffmpeg security link provided in my previous email and my notes as to what version of ffmpeg they were corrected in. This would seem to me that vuxml is not current as of the current maintainers package version. PORTNAME= ffmpeg PORTVERSION=2.8.3 PORTREVISION= 2 PORTEPOCH= 1 Please let me know what I am missing here. Regards, --mikej ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
gnupg-1.4.20.tar.bz2.sig not available by FTP
Dear port maintainer, The port update of gnupg-1.4.20.tar.bz2.sig seems to bump. => Attempting to fetch ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.20.tar.bz2.sig fetch: ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.20.tar.bz2.sig: size mismatch: expected 287, actual 574 => Attempting to fetch http://mirror.tje.me.uk/pub/mirrors/ftp.gnupg.org/gnupg/gnupg-1.4.20.tar.bz2.sig fetch: http://mirror.tje.me.uk/pub/mirrors/ftp.gnupg.org/gnupg/gnupg-1.4.20.tar.bz2.sig: Not Found => Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/gnupg-1.4.20.tar.bz2.sig fetch: http://distcache.FreeBSD.org/ports-distfiles/gnupg-1.4.20.tar.bz2.sig: Not Found => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles// and try again. Can you pls provide an other ftp location so that I can download manually? Thanks, Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: gnupg-1.4.20.tar.bz2.sig not available by FTP
On 24-12-2015 0:00, JosC wrote: Dear port maintainer, The port update of gnupg-1.4.20.tar.bz2.sig seems to bump. => Attempting to fetch ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.20.tar.bz2.sig fetch: ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.20.tar.bz2.sig: size mismatch: expected 287, actual 574 => Attempting to fetch http://mirror.tje.me.uk/pub/mirrors/ftp.gnupg.org/gnupg/gnupg-1.4.20.tar.bz2.sig fetch: http://mirror.tje.me.uk/pub/mirrors/ftp.gnupg.org/gnupg/gnupg-1.4.20.tar.bz2.sig: Not Found => Attempting to fetch http://distcache.FreeBSD.org/ports-distfiles/gnupg-1.4.20.tar.bz2.sig fetch: http://distcache.FreeBSD.org/ports-distfiles/gnupg-1.4.20.tar.bz2.sig: Not Found => Couldn't fetch it - please try to retrieve this => port manually into /usr/ports/distfiles// and try again. I tried to use the ftp location @ https://lists.gnupg.org/pipermail/gnupg-announce/2015q4/000382.html ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.20.tar.bz2 (3606k) ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.20.tar.bz2.sig but the files I downloaded seem to have a mismatch in size too, so that I get the first two error lines from above. BR, Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Failed upgrade graphics/ImageMagick: /usr/bin/ld: skipping incompatible /usr/lib32/...
On Wed, Dec 23, 2015 at 5:14 AM, David Wolfskill wrote: > Today's daily stable/10 laptop update was from: > > FreeBSD g1-252.catwhisker.org 10.2-STABLE FreeBSD 10.2-STABLE #235 > r292590M/292594:1002504: Tue Dec 22 04:31:23 PST 2015 > r...@g1-252.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY amd64 > > to: > > FreeBSD g1-252.catwhisker.org 10.2-STABLE FreeBSD 10.2-STABLE #236 > r292656M/292657:1002504: Wed Dec 23 04:20:06 PST 2015 > r...@g1-252.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY amd64 > > > After a successful reboot, I then (as is my custom) invoked portmaster > to update the installed ports on it; the following were selected: > > ===>>> The following actions will be taken if you choose to proceed: > Upgrade rpm2cpio-1.4 to rpm2cpio-1.4_1 > Upgrade ImageMagick-6.9.2.8_1,1 to ImageMagick-6.9.2.10,1 > Upgrade librsvg2-2.40.10 to librsvg2-2.40.12 > Upgrade libXi-1.7.5,1 to libXi-1.7.6,1 > Upgrade openjdk8-8.66.17 to openjdk8-8.66.17_1 > > > /usr/ports had been updated to 404287 (on ports/head). > > During the initial pass, the ImageMagick update failed; I proceeded > with the remianing 3 (which succeeeded), then re-tried ImageMagick, > which failed again in the same way: > > ... > ===> Building for ImageMagick-6.9.2.10,1 > gmake[2]: Entering directory > '/common/ports/graphics/ImageMagick/work/ImageMagick-6.9.2-10' > gmake all-am > gmake[3]: Entering directory > '/common/ports/graphics/ImageMagick/work/ImageMagick-6.9.2-10' > cp -f magick/ImageMagick.pc magick/ImageMagick-6.pc > cp -f magick/MagickCore.pc magick/MagickCore-6.pc > cp -f wand/MagickWand.pc wand/MagickWand-6.pc > cp -f wand/Wand.pc wand/Wand-6.pc > cp -f Magick++/lib/Magick++.pc Magick++/lib/Magick++-6.pc > cp -f Magick++/lib/ImageMagick++.pc Magick++/lib/ImageMagick++-6.pc > GEN PerlMagick/quantum/Q16HDRI.xs > GEN PerlMagick/quantum/Q16HDRI.pm > CC coders/coders_aai_la-aai.lo > CC magick/magick_libMagickCore_6_la-animate.lo > ... > CC utilities/montage.o > CC utilities/stream.o > CCLD magick/libMagickCore-6.la > /usr/bin/ld: skipping incompatible /usr/lib32/liblzma.so when searching > for -llzma > /usr/bin/ld: skipping incompatible /usr/lib32/liblzma.a when searching for > -llzma > /usr/bin/ld: skipping incompatible /usr/lib32/libbz2.so when searching for > -lbz2 > /usr/bin/ld: skipping incompatible /usr/lib32/libbz2.a when searching for > -lbz2 > /usr/bin/ld: skipping incompatible /usr/lib32/libz.so when searching for > -lz > /usr/bin/ld: skipping incompatible /usr/lib32/libz.a when searching for -lz > /usr/bin/ld: skipping incompatible /usr/lib32/libm.so when searching for > -lm > /usr/bin/ld: skipping incompatible /usr/lib32/libm.a when searching for -lm > /usr/bin/ld: skipping incompatible /usr/lib32/libpthread.so when searching > for -lpthread > /usr/bin/ld: skipping incompatible /usr/lib32/libpthread.a when searching > for -lpthread > /usr/bin/ld: skipping incompatible /usr/lib32/libgcc.a when searching for > -lgcc > /usr/bin/ld: skipping incompatible /usr/lib32/libgcc_s.so when searching > for -lgcc_s > /usr/bin/ld: skipping incompatible /usr/lib32/libpthread.so when searching > for -lpthread > /usr/bin/ld: skipping incompatible /usr/lib32/libpthread.a when searching > for -lpthread > /usr/bin/ld: skipping incompatible /usr/lib32/libc.so.7 when searching for > /usr/lib32/libc.so.7 > /usr/bin/ld: cannot find /usr/lib32/libc.so.7 > cc: error: linker command failed with exit code 1 (use -v to see > invocation) > Makefile:6617: recipe for target 'magick/libMagickCore-6.la' failed > gmake[3]: *** [magick/libMagickCore-6.la] Error 1 > gmake[3]: *** Waiting for unfinished jobs > gmake[3]: Leaving directory > '/common/ports/graphics/ImageMagick/work/ImageMagick-6.9.2-10' > Makefile:5194: recipe for target 'all' failed > gmake[2]: *** [all] Error 2 > gmake[2]: Leaving directory > '/common/ports/graphics/ImageMagick/work/ImageMagick-6.9.2-10' > ===> Compilation failed unexpectedly. > Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to > the maintainer. > *** Error code 1 > > Stop. > make[1]: stopped in /common/ports/graphics/ImageMagick > *** Error code 1 > > Stop. > make: stopped in /common/ports/graphics/ImageMagick > > ===>>> make build failed for graphics/ImageMagick > ===>>> Aborting update > > ===>>> You can restart from the point of failure with this command line: >portmaster graphics/ImageMagick > > Script done on Wed Dec 23 04:40:36 2015 > > > As I am not attempting to cross-build -- this is a native amd64 > environment; no jails; no virtualization -- and building "for local > consumption," I'm not at all clear why the port was looking at > 32-bit libraries in the first place ... but I freely admit that I've > never had occasion to examine that in detail before, so don't take > that as anything more than an admission of ignorance. > > The change to the port itself appears to be quite mino
Re: Reporting fixes so that vuxml can be updated
On Wed, Dec 23, 2015 at 11:26 AM, Michael Jung wrote: > On 2015-12-23 11:55, Lowell Gilbert wrote: > >> Michael Jung writes: >> >> "pkg audit" on my system returns the following CVE's for ffmpeg. I >>> have noted >>> in the list below that http://www.ffmpeg.org/security.html claims >>> these CVE's >>> were fixed in the ffmpeg version noted. >>> >>> Is this the correct place/list to report updates to that vuxml can be >>> updated? >>> >> >> No updates to vuxml are needed (or appropriate). >> >> Update your ffmpeg port and you'll be fine. >> >> > I neglected to state that my port is current > > ffmpeg-2.8.3_2,1 Realtime audio/video encoder/converter and > streaming server > > Yet all the CVE's reported by "pkg audit" have been fixed according to > the ffmpeg security link provided in my previous email and my notes as to > what > version of ffmpeg they were corrected in. > > This would seem to me that vuxml is not current as of the current > maintainers > package version. > > PORTNAME= ffmpeg > PORTVERSION=2.8.3 > PORTREVISION= 2 > PORTEPOCH= 1 > > > Please let me know what I am missing here. > > Regards, > > --mikej > > This has nothing to do with the ffmpeg port and re-installing won't help. The problem is that handbrake and a few other multimedia ports include a specific (old) version of ffmpeg. avidemux has ffmpeg-2.6.1. They do this is to deal with the continual churn in ffmpeg's API and ABI. In recent times ffmpeg developers have tried to stabilize the API, but I'm sure how well it is doing. In any case, handbrake, avidemux and gstreamer-ffmpeg all have this problem. Until those ports are updated to a recent version of ffmpeg, the vulnerability will remain. I hope to try a newer ffmpeg with avidemux when I get time (if I ever do) as I use it far more than I do handbrake. BTW, if you have x265 installed, handbrake will also fail due to a conflict. There is not real conflict. It's a problem with the handbrake port is not properly using the correct header files when x.265 is installed. Just delete x265, build and install handbrake, and re-install x265 until handbrake updates it's internal x265 to newer one. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: gnupg-1.4.20.tar.bz2.sig not available by FTP
Try make makesum. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: gnupg-1.4.20.tar.bz2.sig not available by FTP
The distinfo needs to be SHA256 (gnupg-1.4.20.tar.bz2) = 04988b1030fa28ddf961ca8ff6f0f8984e0cddcb1eb02859d5d8fe0fe237edcc SIZE (gnupg-1.4.20.tar.bz2) = 3692881 SHA256 (gnupg-1.4.20.tar.bz2.sig) = 60699efc9c9546722c04aba69fff874aaf5dacd7d4637238cb8d66960963f843 SIZE (gnupg-1.4.20.tar.bz2.sig) = 574 On 24 December 2015 at 10:35, JosC wrote: > On 24-12-2015 0:00, JosC wrote: > >> Dear port maintainer, >> >> The port update of gnupg-1.4.20.tar.bz2.sig seems to bump. >> >> => Attempting to fetch >> ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.20.tar.bz2.sig >> fetch: ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.20.tar.bz2.sig: size >> mismatch: expected 287, actual 574 >> >> => Attempting to fetch >> http://mirror.tje.me.uk/pub/mirrors/ftp.gnupg.org/gnupg/gnupg-1.4.20.tar.bz2.sig >> fetch: >> http://mirror.tje.me.uk/pub/mirrors/ftp.gnupg.org/gnupg/gnupg-1.4.20.tar.bz2.sig: >> Not Found >> >> => Attempting to fetch >> http://distcache.FreeBSD.org/ports-distfiles/gnupg-1.4.20.tar.bz2.sig >> fetch: >> http://distcache.FreeBSD.org/ports-distfiles/gnupg-1.4.20.tar.bz2.sig: >> Not Found >> >> => Couldn't fetch it - please try to retrieve this >> => port manually into /usr/ports/distfiles// and try again. >> >> I tried to use the ftp location @ > https://lists.gnupg.org/pipermail/gnupg-announce/2015q4/000382.html > > ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.20.tar.bz2 (3606k) > ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.20.tar.bz2.sig > > but the files I downloaded seem to have a mismatch in size too, so that I > get the first two error lines from above. > > BR, Jos Chrispijn > > > > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Failed upgrade graphics/ImageMagick: /usr/bin/ld: skipping incompatible /usr/lib32/...
The old question: Is something in /etc/make.conf ode /etc/libmap.conf, which can cause this errors? ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Failed upgrade graphics/ImageMagick: /usr/bin/ld: skipping incompatible /usr/lib32/...
On Thu, Dec 24, 2015 at 02:00:09AM +0100, Walter Schwarzenfeld wrote: > The old question: Is something in /etc/make.conf ode /etc/libmap.conf, > which can cause this errors? > Well, I don't *think* so, but: g1-252(10.2-S)[1] ls -lT /etc/make.conf -r--r--r-- 1 root wheel 442 Dec 20 06:24:12 2015 /etc/make.conf g1-252(10.2-S)[2] cat !$ cat /etc/make.conf NET_SNMP_SYS_CONTACT="da...@catwhisker.org" NET_SNMP_SYS_LOCATION="variable" NET_SNMP_LOGFILE=/var/log/snmpd.log NET_SNMP_PERSISTENTDIR=/var/net-snmp WITH_BSD_JDK=TRUE # For mplayer WITHOUT_RUNTIME_CPUDETECTION= YES WITHOUT_CJK=YES NO_SUID_XSERVER=YES # For Linux compat OVERRIDE_LINUX_BASE_PORT=c6 OVERRIDE_LINUX_NONBASE_PORTS=c6 INSTALL_AS_NCFTP=yes OPTIONS_SET=OPTIMIZED_CFLAGS # DISABLE_VULNERABILITIES=yes DEFAULT_VERSIONS+= perl5=5.22 g1-252(10.2-S)[3] ls -lT libmap.conf ls: libmap.conf: No such file or directory g1-252(10.2-S)[4] [The relatively recent mtime for make.conf is from the "# DISABLE_VULNERABILITIES=yes" line.] Peace, david -- David H. Wolfskill da...@catwhisker.org Those who would murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: Failed upgrade graphics/ImageMagick: /usr/bin/ld: skipping incompatible /usr/lib32/...
I don't really believe it is cause this errors, but comment out WITHOUT_RUNTIME_CPUDETECTION= YES and OPTIONS_SET=OPTIMIZED_CFLAGS and try it. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: gnupg-1.4.20.tar.bz2.sig not available by FTP
On Thu, 24 Dec 2015 11:57:12 +1100 Dewayne Geraghty wrote > The distinfo needs to be > SHA256 (gnupg-1.4.20.tar.bz2) = > 04988b1030fa28ddf961ca8ff6f0f8984e0cddcb1eb02859d5d8fe0fe237edcc > SIZE (gnupg-1.4.20.tar.bz2) = 3692881 > SHA256 (gnupg-1.4.20.tar.bz2.sig) = > 60699efc9c9546722c04aba69fff874aaf5dacd7d4637238cb8d66960963f843 > SIZE (gnupg-1.4.20.tar.bz2.sig) = 574 Yes. But if upstream re-rolled it. We need to know *why*. Unpack both && diff(1) the trees. --Chris > > > On 24 December 2015 at 10:35, JosC wrote: > > > On 24-12-2015 0:00, JosC wrote: > > > >> Dear port maintainer, > >> > >> The port update of gnupg-1.4.20.tar.bz2.sig seems to bump. > >> > >> => Attempting to fetch > >> ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.20.tar.bz2.sig > >> fetch: ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.20.tar.bz2.sig: size > >> mismatch: expected 287, actual 574 > >> > >> => Attempting to fetch > >> > >> http://mirror.tje.me.uk/pub/mirrors/ftp.gnupg.org/gnupg/gnupg-1.4.20.tar.bz2. > >> sig fetch: > >> > >> http://mirror.tje.me.uk/pub/mirrors/ftp.gnupg.org/gnupg/gnupg-1.4.20.tar.bz2. > >> sig: Not Found > >> > >> => Attempting to fetch > >> http://distcache.FreeBSD.org/ports-distfiles/gnupg-1.4.20.tar.bz2.sig > >> fetch: > >> http://distcache.FreeBSD.org/ports-distfiles/gnupg-1.4.20.tar.bz2.sig: > >> Not Found > >> > >> => Couldn't fetch it - please try to retrieve this > >> => port manually into /usr/ports/distfiles// and try again. > >> > >> I tried to use the ftp location @ > > https://lists.gnupg.org/pipermail/gnupg-announce/2015q4/000382.html > > > > ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.20.tar.bz2 (3606k) > > ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-1.4.20.tar.bz2.sig > > > > but the files I downloaded seem to have a mismatch in size too, so that I > > get the first two error lines from above. > > > > BR, Jos Chrispijn ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Failed upgrade graphics/ImageMagick: /usr/bin/ld: skipping incompatible /usr/lib32/...
On Thu, Dec 24, 2015 at 02:28:24AM +0100, Walter Schwarzenfeld wrote: > I don't really believe it is cause this errors, but comment out > > WITHOUT_RUNTIME_CPUDETECTION= YES and OPTIONS_SET=OPTIMIZED_CFLAGS > > and try it. > ... Thanks for the suggestion; I tried it, but the failure recurred. Peace, david -- David H. Wolfskill da...@catwhisker.org Those who would murder in the name of God or prophet are blasphemous cowards. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: gnupg-1.4.20.tar.bz2.sig not available by FTP
On Thu, 24 Dec 2015, Walter Schwarzenfeld wrote: Try make makesum. Noo! Or at least not unless you realize the security implications of this. It is essentially overriding a warning that the distfiles might have been tampered with. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: gnupg-1.4.20.tar.bz2.sig not available by FTP
Look here: https://lists.gnupg.org/pipermail/gnupg-announce/2015q4/000382.html There it iis 574. Seems an error by the maintainer. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Failed upgrade graphics/ImageMagick: /usr/bin/ld: skipping incompatible /usr/lib32/...
On Wed, Dec 23, 2015 at 5:36 PM, David Wolfskill wrote: > On Thu, Dec 24, 2015 at 02:28:24AM +0100, Walter Schwarzenfeld wrote: > > I don't really believe it is cause this errors, but comment out > > > > WITHOUT_RUNTIME_CPUDETECTION= YES and OPTIONS_SET=OPTIMIZED_CFLAGS > > > > and try it. > > ... > > Thanks for the suggestion; I tried it, but the failure recurred. > > Peace, > david > -- > David H. Wolfskill da...@catwhisker.org > Those who would murder in the name of God or prophet are blasphemous > cowards. > I seriously doubt that it will make a difference, but why not just move make.conf and src.conf aside for a quick test? That should remove any possibility. I am now updating my system. I'll try re-building ImageMagick as soon as it finishes (allowing for delay while we have dinner). -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com ___ freebsd-ports@freebsd.org mailing list https://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 +-+ devel/gdcm | 2.4.4 | 2.6.2 +-+ science/metaf2xml | 1.57| 1.58 +-+ 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 https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Failed upgrade graphics/ImageMagick: /usr/bin/ld: skipping incompatible /usr/lib32/...
On Wed, Dec 23, 2015 at 6:11 PM, Kevin Oberman wrote: > On Wed, Dec 23, 2015 at 5:36 PM, David Wolfskill > wrote: > >> On Thu, Dec 24, 2015 at 02:28:24AM +0100, Walter Schwarzenfeld wrote: >> > I don't really believe it is cause this errors, but comment out >> > >> > WITHOUT_RUNTIME_CPUDETECTION= YES and OPTIONS_SET=OPTIMIZED_CFLAGS >> > >> > and try it. >> > ... >> >> Thanks for the suggestion; I tried it, but the failure recurred. >> >> Peace, >> david >> -- >> David H. Wolfskill da...@catwhisker.org >> Those who would murder in the name of God or prophet are blasphemous >> cowards. >> > > > > I seriously doubt that it will make a difference, but why not just move > make.conf and src.conf aside for a quick test? That should remove any > possibility. > > I am now updating my system. I'll try re-building ImageMagick as soon as > it finishes (allowing for delay while we have dinner). > I can now confirm that it is the system. After updating 10-STABLE to r292678, I get the same lib32 errors when building ImageMagick. I can try bisecting, but it's too late tonight and I have to work tomorrow AM and then finish wrapping packages. (Packages will be a TOP priority.) The problem has to be fairly recent as graphics/ImageMagik has had several updates recently. I'd try backing off about a week at the most as a starting point. :Looks like the most likely place is the linker. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Failed upgrade graphics/ImageMagick: /usr/bin/ld: skipping incompatible /usr/lib32/...
Seems only STABLE. On 10-2-RELEASE amd64 and i386 and on 9.3-RELEASE also both compiles fine. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: Failed upgrade graphics/ImageMagick: /usr/bin/ld: skipping incompatible /usr/lib32/...
It's definitely 10-STABLE and a fairly recent change. It MIGHT be in HEAD, as well, but I don't have anything running HEAD ATM. It's nothing older than a couple of weeks. Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkober...@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 On Wed, Dec 23, 2015 at 10:45 PM, Walter Schwarzenfeld < w.schwarzenf...@utanet.at> wrote: > Seems only STABLE. On 10-2-RELEASE amd64 and i386 and on 9.3-RELEASE > also both compiles fine. > ___ > freebsd-ports@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org" > ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
