Re: hung poudriere bulk recovery
Got a hung poudriere run last night: On 10/28/15 15:10, Bryan Drewery wrote: On 10/23/2015 9:34 AM, Russell L. Carter wrote: Greetings, Recently my nightly cron poudriere builds have been occasionally hanging. For instance, here's last night's, with apparently no progress for over 10 hours: root@terpsichore> poudriere status SET PORTS JAILBUILDSTATUS QUEUE BUILT FAIL SKIP IGNORE REMAIN TIME LOGS - default 10-stable-amd64 2015-10-22_22h30m08s parallel_build 488 3400 0454 10:45:56 /ssd1/poudriere/data/logs/bulk/10-stable-amd64-default/2015-10-22_22h30m08s root@terpsichore> Also check 'poudriere status -b' to see per-builder status. Something may be actually doing something. Poudriere will timeout builds after a long time. I forget the default but it may be up to 24 hours. root@terpsichore> date Fri Oct 30 15:19:55 MST 2015 root@terpsichore> poudriere status -b [10-stable-amd64-default] [2015-10-29_22h30m07s] [parallel_build:] Queued: 129 Built: 34 Failed: 0 Skipped: 0 Ignored: 0 Tobuild: 95 Time: 16:49:55 [01]: x11-toolkits/gtk30 build_port_done (16:40:58) [02]: graphics/ImageMagick build_port_done (16:43:16) [03]: www/webkit-gtk2 build_port_done (16:43:58) >> Logs: /ssd1/poudriere/data/logs/bulk/10-stable-amd64-default/2015-10-29_22h30m07s root@terpsichore> Please record 'procstat -kka' before rebooting in case this is some kind of deadlock. invoked right after the poudriere status -b: http://rcarter.esturion.net/procstat-kka.txt I'm not sure how to debug this, but in the interim, I'm very curious how I can stop the hung bulk run, and either restart it, or clean up the various mounted zfs filesystems and manually restart from the beginning w/o rebooting. Studying the man page, it's not clear at all the Right Way to do this, so any pointers here would be appreciated. Kill -TERM the main poudriere process. It will clean up children. Beyond that you can 'poudriere jail -j NAME -p TREE -z SET -k' to clean up any mounts leftover from a previous build. A bit of trial and error led me to this solution, without either '-p' or '-z', so I'm good. In the above, I ran the exact same bulk script manually and the poudriere bulk build ran to completion. Thanks! Russell ___ 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: OpenCASCADE 6.9.1
On 10/19/15 21:36, Thierry Thomas wrote: Nothing special, but I've been travelling in Africa, and now I'm late with my ports... ATM I'm working on Code_Aster, so if you have some time to work on OpenCASCADE, that would be fine! Thanks Hello. This is what I've come up with, by modifying your port. You might want to check because portlint/porttools give some warnings. Also, due to the obsolescence and vulnerability of freeimage, I didn't even try to build with VIS. bye & Thanks av. opencascade691_port.tbz Description: Binary data ___ 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/omniORB-4.1 | 4.1.7 | 4.2.1-2 +-+ 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"
security/vpnc: Redistribution is not allowed if linked against OpenSSL
The vpnc port has the following:
LEGAL_TEXT= Redistribution is not allowed if linked against OpenSSL
.if ${PORT_OPTIONS:MSSL}
NO_PACKAGE= binary linked against OpenSSL must not be redistributed
CFLAGS+=-DOPENSSL_GPL_VIOLATION
Could anyone explain why this is an issue?
pgpDIGYBIe6Ou.pgp
Description: PGP signature
phpMyAdmin port upgrade
___ 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 Port: games/joequake
Hi, I like toinform that this port is building ok (my system is an amd/64), but on runtime it fails, sayng that an "security module" was not found. output of invocation: *1023:flavio@frisbie:~/teco/projects/estudo/Machine_learning/week1% joequake-x11 * *Added packfile /usr/local/share/quake/id1/pak0.pak (339 files)* *Added packfile /usr/local/share/quake/id1/pak1.pak (85 files)* *Added packfile /usr/local/share/quake/joequake/pak0.pak (48 files)* *Console initialized* *[02]Security module not found* *Segmentation fault (core dumped)* Best regards, Flávio Sent from my coffemaker ___ 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: OpenCASCADE 6.9.1
Hi! > This is what I've come up with, by modifying your port. > You might want to check because portlint/porttools give some warnings. > > Also, due to the obsolescence and vulnerability of freeimage, I didn't > even try to build with VIS. I had a quick look at this. There's no public distfile, only available if one registers ? -- p...@opsec.eu+49 171 3101372 5 years to go ! ___ 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"
