Package Quarterly 104 amd64/i386 cannot build math/saga
The package builders for 104amd64-quarterly and 104i386-quarterly complain about a build problem with math/saga[1][2]. This happens, because 104 uses the outdated math/saga version 6.3.0. In HEAD, there is already a working version 6.4.0 for some time now. Is it possible to also update the quarterly packages to version 6.4.0? Thanks for any clarification. Regards, Rainer Hurling [1] http://beefy2.nyi.freebsd.org/data/104amd64-quarterly/474918/logs/errors/saga-6.3.0.log [2] http://beefy4.nyi.freebsd.org/data/104i386-quarterly/474918/logs/saga-6.3.0.log ___ 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 +-+ www/gobuffalo | 0.10.3 | v0.12.4 +-+ x11-fm/filerunner | 17.04.01.19 | 18.07.19.16 +-+ 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"
After mutt-1.10.0_1 -> mutt-1.10.1 upgrade, gnupg fails
This is running: FreeBSD g1-215.catwhisker.org 11.2-STABLE FreeBSD 11.2-STABLE #685 r336523M/336541:1102501: Fri Jul 20 03:40:05 PDT 2018 r...@g1-215.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY amd64 and after updating all installed ports to reflect the ports "head" branch at r475002. A symptom is that an attempt to send a signed, unencrypted message yields a failure, with the messages: | gpg: skipped "0x6757003D": Unusable secret key | gpg: signing failed: Unusable secret key This works on another machine (the one I'm using to send this message), with the same gnupg/mutt setup, but running mutt-1.10.0_1. I have not configured mutt to use gpgme, though I'm willing to try it. I recall that I needed to tweak ~/.muttrc a bit after the gnupg-2.0 -> gnupg-2.1 update -- though that change was merely commenting out the 'pgp_verify_command' line. I note that a result of the mutt upgrade is that /usr/local/share/examples/mutt/gpg.rc has changed, but that change was merely to remove the pgp_decryption_okay setting (which I don't have) and add 'set pgp_check_gpg_decrypt_status_fd'; I tried adding that, to no avail. Any hints or suggestions? Thanks! Peace, david -- David H. Wolfskill da...@catwhisker.org Trump is providing aid and comfort to a regime that is hostile to US interests. See http://www.catwhisker.org/~david/publickey.gpg for my public key. signature.asc Description: PGP signature
Re: After mutt-1.10.0_1 -> mutt-1.10.1 upgrade, gnupg fails
On Fri, Jul 20, 2018 at 6:53 AM David Wolfskill wrote: > > This is running: > > FreeBSD g1-215.catwhisker.org 11.2-STABLE FreeBSD 11.2-STABLE #685 > r336523M/336541:1102501: Fri Jul 20 03:40:05 PDT 2018 > r...@g1-215.catwhisker.org:/common/S1/obj/usr/src/sys/CANARY amd64 > > and after updating all installed ports to reflect the ports "head" > branch at r475002. > > A symptom is that an attempt to send a signed, unencrypted message > yields a failure, with the messages: > > | gpg: skipped "0x6757003D": Unusable secret key > | gpg: signing failed: Unusable secret key > > This works on another machine (the one I'm using to send this > message), with the same gnupg/mutt setup, but running mutt-1.10.0_1. > > I have not configured mutt to use gpgme, though I'm willing to try > it. I recall that I needed to tweak ~/.muttrc a bit after the > gnupg-2.0 -> gnupg-2.1 update -- though that change was merely > commenting out the 'pgp_verify_command' line. > > I note that a result of the mutt upgrade is that > /usr/local/share/examples/mutt/gpg.rc has changed, but that change > was merely to remove the pgp_decryption_okay setting (which I don't > have) and add 'set pgp_check_gpg_decrypt_status_fd'; I tried adding > that, to no avail. > > Any hints or suggestions? > > Thanks! > > Peace, > david Hi, David! FWIW, I'd highly suggest using gpgme. set crypt_use_gpgme=yes has replaced my entire gnupg command file. gnupg was just updated to 2.2.9 a few days ago, so that might be the cause (and not mutt). Are you able to successfully use that key from the command-line? # Adam -- Adam Weinberger ad...@adamw.org https://www.adamw.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"
