FreeBSD Port: terminator-1.0 error on i386
% terminator Traceback (most recent call last): File "/usr/local/bin/terminator", line 63, in ibus_running = [p for p in psutil.process_iter() if p.name == 'ibus-daemon' and p.username == username] File "/usr/local/lib/python2.7/site-packages/psutil/__init__.py", line 1562, in process_iter yield add(pid) File "/usr/local/lib/python2.7/site-packages/psutil/__init__.py", line 1537, in add proc = Process(pid) File "/usr/local/lib/python2.7/site-packages/psutil/__init__.py", line 442, in __init__ self._init(pid) File "/usr/local/lib/python2.7/site-packages/psutil/__init__.py", line 469, in _init self.create_time() File "/usr/local/lib/python2.7/site-packages/psutil/__init__.py", line 819, in create_time self._create_time = self._proc.create_time() File "/usr/local/lib/python2.7/site-packages/psutil/_psbsd.py", line 561, in wrapper return fun(self, *args, **kwargs) File "/usr/local/lib/python2.7/site-packages/psutil/_psbsd.py", line 735, in create_time return self.oneshot()[kinfo_proc_map['create_time']] File "/usr/local/lib/python2.7/site-packages/psutil/_psbsd.py", line 561, in wrapper return fun(self, *args, **kwargs) File "/usr/local/lib/python2.7/site-packages/psutil/_common.py", line 344, in wrapper return fun(self) File "/usr/local/lib/python2.7/site-packages/psutil/_psbsd.py", line 618, in oneshot ret = cext.proc_oneshot_info(self.pid) SystemError: NULL object passed to Py_BuildValue 12.0-STABLE i386 All ports from pkg -- - Alex. ___ 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: CLISP (2.49.93+) re-ported
Hi! > I've re-ported lang/clisp [1]. Cool, thanks, committed! Please note that quite a few other ports were removed at that time, because they depend on lang/clisp: devel/cl-cffi-clisp||2014-07-28|Has expired: Depends on deprecated lang/clisp devel/cl-alexandria-clisp||2014-07-28|Has expired: Depends on deprecated lang/clisp converters/cl-babel-clisp||2014-07-28|Has expired: Depends on deprecated lang/clisp devel/cl-infix-clisp||2014-07-28|Has expired: Depends on deprecated lang/clisp devel/meta-cvs||2014-07-28|Has expired: Depends on deprecated lang/clisp textproc/cl-meta-clisp||2014-07-28|Has expired: Depends on deprecated lang/clisp www/cl-lml-clisp||2014-07-28|Has expired: Depends on deprecated lang/clisp devel/cl-trivial-features-clisp||2014-07-28|Has expired: Depends on deprecated lang/clisp security/cl-md5-clisp||2014-07-28|Has expired: Depends on deprecated lang/clisp devel/cl-port-clisp||2014-07-28|Has expired: Depends on deprecated lang/clisp textproc/cl-ppcre-clisp||2014-07-28|Has expired: Depends on deprecated lang/clisp devel/cl-asdf-clisp||2014-07-28|Has expired: Depends on deprecated lang/clisp devel/cl-split-sequence-clisp||2014-07-28|Has expired: Depends on deprecated lang/clisp devel/cl-trivial-gray-streams-clisp||2014-07-28|Has expired: Depends on deprecated lang/clisp Please check if you can provide updates for those as well. > This port has been removed > since 2014-07-28 because it's development has ceased. But it > continue to developed with GitLab [2]. Latest version is > 2.49.93+ and last commitment was in 12 Nov, 2018. I've > reconstructed to suit this latest version and worked fine > without sevral features: > > CLX_NEW Faster X11 Interface (replaces clx/mit-clx) > GLIBC Interface to most of the GNU libc library > JITC Use a given Just-In-Time Compiler > MATLABMatrix calculations using Matlab > NETICABayesian belief networks and influence diagrams > ORACLEOracle RDMBS interface > PARI PARI Computer Algebra System > > These were all faild to compile with gcc8. My working > environments are as follows: > > admin@jdtpkx:~ % uname -a > FreeBSD jdtpkx 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r339677M: Fri Oct 26 > 14:56:49 JST 2018 root@msrvkx:/usr/obj/usr/src/amd64.amd64/sys/XIJ amd64 > admin@jdtpkx:~ % svnlite info --show-item revision /usr/ports > 486173 > admin@jdtpkx:~ % > > I'm willing to report to test [1] and how to resolve above > problems. Thanks very much! Just submit patches to https://bugs.freebsd.org/ if you have fixes for those OPTIONs. -- p...@opsec.eu+49 171 3101372One year 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"
Re: How to use @preexec to test for installed packages
On Sat, Apr 6, 2019 at 12:49 PM Miroslav Lachman <000.f...@quip.cz> wrote: > > Matthew Seaman wrote on 2019/04/06 19:00: > > On 06/04/2019 14:58, Matthias Fechner wrote: > > > >> as pkg cannot handle CONFLICTS_INSTALL I tried now to implement this as > >> a preinstall command using @preexec in pkg-plist. > >> > >> The command should check if a package is installed and stop the > >> installation or continue if the package is not installed. > >> > >> I tried it with the following command: > >> @preexec `/usr/sbin/pkg -N info -e gogs`; if [ $? -eq 0 ]; then echo > >> "Gitlab cannot be installed together with gogs as both of them modify > >> .ssh/authorized_keys" && exit 1; else echo "Gogs not installed, > >> continue."; fi > >> > >> But it does not work. > >> Now matter if gogs is installed or not. > >> If I execute the same line in a shell script, it works fine. > >> > >> Anyone an idea? > > > > pkg(8) does handle the most common reason for packages conflicting at > > install time -- file name clashes. Indeed, it does this automatically > > with no need of input from porters or maintainers, although it is usual > > to add CONFLICTS_INSTALL lines to port Makefiles to document clashes > > discovered this way. > > > > However, where there are other reasons for packages to conflict at > > install time, then you are correct that pkg doesn't handle this. > > There's simply no mechanism to include information about package > > conflicts into pkg metadata. > > Then you can add some fake (empty) file to the plist of package A which > will conflict with package B and then pkg conflict will work as expected. > But I am not sure we should prevent installation of some package just > because it uses authorized_keys too. Especially since www/gitea does the same thing (and probably a number of others as well). # 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"
Re: How to use @preexec to test for installed packages
Matthew Seaman wrote on 2019/04/06 19:00: On 06/04/2019 14:58, Matthias Fechner wrote: as pkg cannot handle CONFLICTS_INSTALL I tried now to implement this as a preinstall command using @preexec in pkg-plist. The command should check if a package is installed and stop the installation or continue if the package is not installed. I tried it with the following command: @preexec `/usr/sbin/pkg -N info -e gogs`; if [ $? -eq 0 ]; then echo "Gitlab cannot be installed together with gogs as both of them modify .ssh/authorized_keys" && exit 1; else echo "Gogs not installed, continue."; fi But it does not work. Now matter if gogs is installed or not. If I execute the same line in a shell script, it works fine. Anyone an idea? pkg(8) does handle the most common reason for packages conflicting at install time -- file name clashes. Indeed, it does this automatically with no need of input from porters or maintainers, although it is usual to add CONFLICTS_INSTALL lines to port Makefiles to document clashes discovered this way. However, where there are other reasons for packages to conflict at install time, then you are correct that pkg doesn't handle this. There's simply no mechanism to include information about package conflicts into pkg metadata. Then you can add some fake (empty) file to the plist of package A which will conflict with package B and then pkg conflict will work as expected. But I am not sure we should prevent installation of some package just because it uses authorized_keys too. Miroslav Lachman ___ 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: How to use @preexec to test for installed packages
On 06/04/2019 14:58, Matthias Fechner wrote: > as pkg cannot handle CONFLICTS_INSTALL I tried now to implement this as > a preinstall command using @preexec in pkg-plist. > > The command should check if a package is installed and stop the > installation or continue if the package is not installed. > > I tried it with the following command: > @preexec `/usr/sbin/pkg -N info -e gogs`; if [ $? -eq 0 ]; then echo > "Gitlab cannot be installed together with gogs as both of them modify > .ssh/authorized_keys" && exit 1; else echo "Gogs not installed, > continue."; fi > > But it does not work. > Now matter if gogs is installed or not. > If I execute the same line in a shell script, it works fine. > > Anyone an idea? pkg(8) does handle the most common reason for packages conflicting at install time -- file name clashes. Indeed, it does this automatically with no need of input from porters or maintainers, although it is usual to add CONFLICTS_INSTALL lines to port Makefiles to document clashes discovered this way. However, where there are other reasons for packages to conflict at install time, then you are correct that pkg doesn't handle this. There's simply no mechanism to include information about package conflicts into pkg metadata. Now, it shouldn't be beyond the bounds of possibility to include this as input that the pkg solver could use, but it may require quite a deep dive into the bowels of pkg code. I doubt that using @preexec commands in the pkg-plist is going to be very satisfactory -- the end result is that pkg will end up trying to install conflicting packages and then abort in the middle of installation, which could well result in an inconsistent pkg database and user frustration. Cheers, Matthew signature.asc Description: OpenPGP digital signature
Re: How to use @preexec to test for installed packages
Am 06.04.2019 um 18:01 schrieb Adam Weinberger: > What you're describing is > Makefile: > CONFLICTS_INSTALL= gogs does not work, please see here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234807 Gruß Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook ___ 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: How to use @preexec to test for installed packages
On Sat, Apr 6, 2019 at 7:59 AM Matthias Fechner wrote: > > Dear all, > > as pkg cannot handle CONFLICTS_INSTALL I tried now to implement this as > a preinstall command using @preexec in pkg-plist. > > The command should check if a package is installed and stop the > installation or continue if the package is not installed. > > I tried it with the following command: > @preexec `/usr/sbin/pkg -N info -e gogs`; if [ $? -eq 0 ]; then echo > "Gitlab cannot be installed together with gogs as both of them modify > .ssh/authorized_keys" && exit 1; else echo "Gogs not installed, > continue."; fi > > But it does not work. > Now matter if gogs is installed or not. > If I execute the same line in a shell script, it works fine. > > Anyone an idea? What you're describing is Makefile: CONFLICTS_INSTALL= gogs -- 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"
Re: CLISP (2.49.93+) re-ported
Built and slightly runtime tested with default options. +1 for getting this back into the ports collection. On 03.04.2019 00:52, KIRIYAMA Kazuhiko wrote: Hi all, I've re-ported lang/clisp [1]. This port has beed moved since 2014-07-28 because it's development has ceased. But it continue to developed with GitLab [2]. Latest version is 2.49.93+ and last commitment was in 12 Nov, 2018. I've reconstructed to suit this latest version and worked fine without sevral features: CLX_NEW Faster X11 Interface (replaces clx/mit-clx) GLIBC Interface to most of the GNU libc library JITCUse a given Just-In-Time Compiler MATLAB Matrix calculations using Matlab NETICA Bayesian belief networks and influence diagrams ORACLE Oracle RDMBS interface PARIPARI Computer Algebra System These were all faild to compile with gcc8. My working environments are as follows: admin@jdtpkx:~ % uname -a FreeBSD jdtpkx 13.0-CURRENT FreeBSD 13.0-CURRENT #0 r339677M: Fri Oct 26 14:56:49 JST 2018 root@msrvkx:/usr/obj/usr/src/amd64.amd64/sys/XIJ amd64 admin@jdtpkx:~ % svnlite info --show-item revision /usr/ports 486173 admin@jdtpkx:~ % I'm willing to report to test [1] and how to resolve above problems. Best regards [1] https://github.com/TrueFC/ports/tree/master/lang/clisp [2] https://gitlab.com/gnu-clisp/clisp --- KIRIYAMA Kazuhiko ___ 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: How to use @preexec to test for installed packages
On Sat, 6 Apr 2019 15:58:48 +0200 Matthias Fechner wrote: > Dear all, > > as pkg cannot handle CONFLICTS_INSTALL I tried now to implement this > as a preinstall command using @preexec in pkg-plist. > > The command should check if a package is installed and stop the > installation or continue if the package is not installed. > > I tried it with the following command: > @preexec `/usr/sbin/pkg -N info -e gogs`; if [ $? -eq 0 ]; then echo > "Gitlab cannot be installed together with gogs as both of them modify > .ssh/authorized_keys" && exit 1; else echo "Gogs not installed, > continue."; fi > > But it does not work. > Now matter if gogs is installed or not. > If I execute the same line in a shell script, it works fine. > > Anyone an idea? I think you'll find it has to be ONE command. So use && instead of the first semicolon. ___ 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"
How to use @preexec to test for installed packages
Dear all, as pkg cannot handle CONFLICTS_INSTALL I tried now to implement this as a preinstall command using @preexec in pkg-plist. The command should check if a package is installed and stop the installation or continue if the package is not installed. I tried it with the following command: @preexec `/usr/sbin/pkg -N info -e gogs`; if [ $? -eq 0 ]; then echo "Gitlab cannot be installed together with gogs as both of them modify .ssh/authorized_keys" && exit 1; else echo "Gogs not installed, continue."; fi But it does not work. Now matter if gogs is installed or not. If I execute the same line in a shell script, it works fine. Anyone an idea? Gruß Matthias -- "Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the universe trying to produce bigger and better idiots. So far, the universe is winning." -- Rich Cook ___ 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/ocaml-re | 1.4.1 | 1.9.0 +-+ 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"
