Re: [new] hatop-0.7.7
Thank you for reviewing the port and for simplifying it! Patched port is attached. If anyone is interested in testing the runtime, steps are: - install hatop from ports, it will install haproxy as well - add following lines to /etc/haproxy/haproxy.cfg under "global" section: stats socket /var/run/haproxy.sock mode 666 level admin stats timeout 2m - restart haproxy: # /etc/rc.d/haproxy restart - launch hatop with hatop -s /var/run/haproxy.sock haproxy should show some dummy services that are configured by default. To clean up, uninstall hatop and haproxy and remove /etc/haproxy/haproxy.cfg Best, -ljuba On 19.05, Stuart Henderson wrote: > On 2018/05/18 23:24, Ljuba Nedeljkovic wrote: > > Slightly improved port, using variables instead of > > hard coded version numbers > > Here's a diff on top of yours, and please remove the patch: > > - COMMENT typo > - no need to use V, the version is only referenced once > - license say "GPLv3 or later" -> use GPLv3+ > - let MASTER_SITES work even if MASTER_SITE_GOOGLECODE expands > to more than one URL (it's a user-changeable setting) > - drop the MODPY_VERSION, this is the default anyway > - replace patch + SUBST_CMD with MODPY_ADJ_FILES > > I don't use haproxy so can't test runtime. > > > > --- Makefile.orig Sat May 19 01:19:06 2018 > +++ Makefile Sat May 19 01:20:44 2018 > @@ -1,9 +1,8 @@ > # $OpenBSD$ > > -COMMENT =interactive ncurses client for haroxy > +COMMENT =interactive ncurses client for haproxy > > -V = 0.7.7 > -DISTNAME = hatop-${V} > +DISTNAME = hatop-0.7.7 > > CATEGORIES = net > > @@ -11,23 +10,19 @@ HOMEPAGE = > http://feurix.org/projects/hatop/ > > MAINTAINER = Ljuba Nedeljkovic <ljuba@gmail.com> > > -# GPLv3 > +# GPLv3+ > PERMIT_PACKAGE_CDROM = Yes > > -MASTER_SITES = ${MASTER_SITE_GOOGLECODE}hatop/ > +MASTER_SITES = ${MASTER_SITE_GOOGLECODE:=hatop/} > > MODULES =lang/python > -MODPY_VERSION = ${MODPY_DEFAULT_VERSION_2} > > RUN_DEPENDS =net/haproxy > > NO_BUILD = Yes > NO_TEST =Yes > > -SUBST_VARS +=MODPY_VERSION > - > -pre-install: > - ${SUBST_CMD} ${WRKSRC}/bin/hatop > +MODPY_ADJ_FILES =bin/hatop > > do-install: > ${INSTALL_SCRIPT} ${WRKSRC}/bin/hatop ${PREFIX}/bin/ > hatop-0.7.7.tar.gz Description: Binary data
[new] hatop-0.7.7
Slightly improved port, using variables instead of hard coded version numbers Cheers, -ljuba On 12.05, Ljuba Nedeljkovic wrote: > Hello, > > Attached is the port of hatop-0.7.7, interactive ncurses > client for haroxy > > > $ cat pkg/DESCR > > HATop is an interactive ncurses client and real-time monitoring, > statistics displaying tool for the HAProxy TCP/HTTP load balancer. > > HATop's appearance is similar to top(1). It supports various modes for > detailed statistics of all configured proxies and services in near realtime. > In addition, it features an interactive CLI for the haproxy unix socket. > This allows administrators to control the given haproxy instance > (change server weight, put servers into maintenance mode, ...) directly out > of hatop (using keybinds or the CLI) and monitor the results immediately. > > --- > > Project is dormant for some time but it is pretty handy > as is. It is hosted on both google code and github. > I opted for retrieving release tarball from google since > github hosted project does not have proper releases and it > seems to me that GH_* clutter is not popular these days. > > Any test results, comments, even cursing is welcome and > highly appreciated. > > Best, > -ljuba hatop-0.7.7.tar.gz Description: Binary data
Re: NEW: textproc/qrcode
On 12.05, Klemens Nanni wrote: > On Sat, May 12, 2018 at 11:33:11AM +0200, Klemens Nanni wrote: > > On Sat, May 12, 2018 at 10:27:20AM +0200, Ingo Feinerer wrote: > > > please find attached a port for qrcode, a pure python QR Code generator: > > > https://github.com/lincolnloop/python-qrcode > > Looks good, but some tests fail, test.log attached. > ... here it is. > running test > running egg_info > writing qrcode.egg-info/PKG-INFO > writing dependency_links to qrcode.egg-info/dependency_links.txt > writing entry points to qrcode.egg-info/entry_points.txt > writing requirements to qrcode.egg-info/requires.txt > writing top-level names to qrcode.egg-info/top_level.txt > reading manifest file 'qrcode.egg-info/SOURCES.txt' > reading manifest template 'MANIFEST.in' > writing manifest file 'qrcode.egg-info/SOURCES.txt' > running build_ext > test_bad_factory (qrcode.tests.test_script.ScriptTest) ... ok > test_factory (qrcode.tests.test_script.ScriptTest) ... ok > test_isatty (qrcode.tests.test_script.ScriptTest) ... ok > test_optimize (qrcode.tests.test_script.ScriptTest) ... ok > test_piped (qrcode.tests.test_script.ScriptTest) ... ok > test_stdin (qrcode.tests.test_script.ScriptTest) ... ok > test_stdin_py3_unicodedecodeerror (qrcode.tests.test_script.ScriptTest) ... ok > test_change (qrcode.tests.test_release.UpdateManpageTests) ... > /usr/local/lib/python3.6/re.py:212: FutureWarning: split() requires a > non-empty pattern match. > return _compile(pattern, flags).split(string, maxsplit) > ok > test_invalid_data (qrcode.tests.test_release.UpdateManpageTests) ... FAIL > test_no_change (qrcode.tests.test_release.UpdateManpageTests) ... FAIL > test_not_qrcode (qrcode.tests.test_release.UpdateManpageTests) ... ok > test_add_qrdata (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_basic (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_fit (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_get_matrix (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_get_matrix_border (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_invalid_version (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_large (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_mode_8bit (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_mode_8bit_newline (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_mode_alpha (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_mode_number (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_negative_size_at_construction (qrcode.tests.test_qrcode.QRCodeTests) ... > ok > test_negative_size_at_usage (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_optimize (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_optimize_short (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_optimize_size (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_overflow (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_print_ascii (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_print_ascii_stdout (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_print_tty (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_print_tty_stdout (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_qrcode_bad_factory (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_qrcode_factory (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_qrdata_repr (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_regression_mode_comma (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_render_pil (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_render_pymaging_png (qrcode.tests.test_qrcode.QRCodeTests) ... skipped > 'Requires pymaging with PNG support' > test_render_pymaging_png_bad_kind (qrcode.tests.test_qrcode.QRCodeTests) ... > skipped 'Requires pymaging' > test_render_svg (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_render_svg_fragment (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_render_svg_path (qrcode.tests.test_qrcode.QRCodeTests) ... ok > test_render_svg_with_background (qrcode.tests.test_qrcode.QRCodeTests) ... ok > runTest (qrcode.tests.test_qrcode.ShortcutTest) ... ok > runTest (qrcode.tests.test_example.ExampleTest) ... ok > pure (unittest.loader._FailedTest) ... ERROR > > == > ERROR: pure (unittest.loader._FailedTest) > -- > ImportError: Failed to import test module: pure > Traceback (most recent call last): > File "/usr/local/lib/python3.6/unittest/loader.py", line 153, in > loadTestsFromName > module = __import__(module_name) > File "/tmp/pobj/qrcode-6.0/qrcode-6.0/qrcode/image/pure.py", line 1, in > > from pymaging import Image > ModuleNotFoundError: No module named 'pymaging' > This one fails because module is missing. We do not have `pymaging` in ports so, either make the test skip (bad) or port the python module first and include it in TEST_DEPENDS > > == > FAIL:
[new] hatop-0.7.7
Hello, Attached is the port of hatop-0.7.7, interactive ncurses client for haroxy $ cat pkg/DESCR HATop is an interactive ncurses client and real-time monitoring, statistics displaying tool for the HAProxy TCP/HTTP load balancer. HATop's appearance is similar to top(1). It supports various modes for detailed statistics of all configured proxies and services in near realtime. In addition, it features an interactive CLI for the haproxy unix socket. This allows administrators to control the given haproxy instance (change server weight, put servers into maintenance mode, ...) directly out of hatop (using keybinds or the CLI) and monitor the results immediately. --- Project is dormant for some time but it is pretty handy as is. It is hosted on both google code and github. I opted for retrieving release tarball from google since github hosted project does not have proper releases and it seems to me that GH_* clutter is not popular these days. Any test results, comments, even cursing is welcome and highly appreciated. Best, -ljuba hatop-0.7.7.tar.gz Description: Binary data
Re: [NEW] devel/py-yapf
Works for me on amd64, no issues Cheers, On Mon, May 7, 2018 at 9:29 AM, Remi Pointelwrote: > Hi, > > attached is the port of yapf: a formatter Python code. > > -- > $ pkg_info py-yapf > Information for inst:py-yapf-0.21.0 > > Comment: > formatter for Python code > > Description: > YAPF is a formatter based off of 'clang-format'. In essence, the algorithm > takes > the code and reformats it to the best formatting that conforms to the style > guide, even if the original code didn't violate the style guide. If the > whole > codebase of a project is simply piped through YAPF whenever modifications > are > made, the style remains consistent throughout the project and there's no > point > arguing about style in every code review. > > Maintainer: The OpenBSD ports mailing-list > > WWW: https://pypi.python.org/pypi/yapf > -- > > Ok? > > Cheers, > > Remi. > -- If you wish to live wisely, ignore sayings -- including this one.
Re: [New] nnn-1.7
Thank you sthen@ for reviewing the port. Attached is the port with suggested changes, problems that kn@ pointed out (thanks!) are fixed as well. Best On Sun, May 6, 2018 at 1:08 PM, Stuart Henderson <s...@spacehopper.org> wrote: > On 2018/05/06 00:01, Ljuba Nedeljkovic wrote: > > Attached is the port of nnn, version 1.8. Upstream is releasing > > source tarball as a formal/proper release so GH_* are gone. > > Patch (present in previous port submissions) is also gone since > > upstream fixed portability issue with shell script. > > > > Tests/comments.suggestions are welcome. > > I'm no fan of this: > > #!/usr/bin/env bash > > It's not deterministic (relies on the user's PATH being set in a certain > way), I would normally patch these to use ${LOCALBASE}/bin/bash like you > had > in earlier versions of your port. > > -- If you wish to live wisely, ignore sayings -- including this one. nnn-1.8.tar.gz Description: application/gzip
Re: [New] nnn-1.7
Attached is the port of nnn, version 1.8. Upstream is releasing source tarball as a formal/proper release so GH_* are gone. Patch (present in previous port submissions) is also gone since upstream fixed portability issue with shell script. Tests/comments.suggestions are welcome. -ljuba On Wed, May 2, 2018 at 9:41 PM, Klemens Nanni <k...@openbsd.org> wrote: > On Sun, Apr 08, 2018 at 10:27:34PM +0200, Ljuba Nedeljkovic wrote: > > > tl;dr: A pull request to create the asset automatically with Travic CI > > > is welcome. Neither do I use Github, nor do I know shit about Travis. > > > > > > Ljuba, can you do that? > > > > Yes > 1.8 is out with stable release tarballs: > > https://github.com/jarun/nnn/releases > -- If you wish to live wisely, ignore sayings -- including this one. nnn-1.8.tar.gz Description: application/gzip
Re: [New] nnn-1.7
On Sun, Apr 8, 2018 at 6:47 PM, Klemens Nanni <k...@openbsd.org> wrote: > On Wed, Apr 04, 2018 at 01:35:35PM +0200, Jeremie Courreges-Anglas wrote: >> On Wed, Apr 04 2018, Ljuba Nedeljkovic <ljuba@gmail.com> wrote: >> > Ping. >> > >> > On Wed, Mar 14, 2018 at 5:13 PM, Klemens Nanni <k...@openbsd.org> wrote: >> >> On Wed, Mar 14, 2018 at 02:37:22AM +0100, Ljuba Nedeljkovic wrote: >> >>> Please find attached updated port's tarball with suggested fixes. One >> >>> deviation from kn's tarball is removal of `patches/patch-nlay` file and >> >>> doing shebang fix using LOCALBASE with `post-extract` target. Said >> >>> patch leaves literal `#!${LOCALBASE}/bin/bash` in installed `nlay` >> >>> script and breaks it. >> >> Not a fan of modyfing WRKSRC "manually", we have patches and SUBST_CMD >> >> for that. You'd simply patch LOCALBASE into the shebang and later do >> >> >> >> pre-configure: >> >> ${SUBST_CMD} ${WRKSRC}/nlay >> >> >> >> I'm happy to import your latest tarball with that, OK anyone? >> >> Looks good to me, however I'd like us to stop importing ports using >> GH_*. Upstream already uses publishes release assets: >> >> https://github.com/jarun/nnn/releases >> >> Could someone get in touch with them and ask them to publish proper >> source tarballs? > I had a lengthy email conversation with upstream about it. > > tl;dr: A pull request to create the asset automatically with Travic CI > is welcome. Neither do I use Github, nor do I know shit about Travis. > > Ljuba, can you do that? Yes -- If you wish to live wisely, ignore sayings -- including this one.
Re: [New] nnn-1.7
On Wed, Apr 4, 2018 at 1:35 PM, Jeremie Courreges-Anglas <j...@wxcvbn.org> wrote: > On Wed, Apr 04 2018, Ljuba Nedeljkovic <ljuba@gmail.com> wrote: >> Ping. >> >> On Wed, Mar 14, 2018 at 5:13 PM, Klemens Nanni <k...@openbsd.org> wrote: >>> On Wed, Mar 14, 2018 at 02:37:22AM +0100, Ljuba Nedeljkovic wrote: >>>> Please find attached updated port's tarball with suggested fixes. One >>>> deviation from kn's tarball is removal of `patches/patch-nlay` file and >>>> doing shebang fix using LOCALBASE with `post-extract` target. Said >>>> patch leaves literal `#!${LOCALBASE}/bin/bash` in installed `nlay` >>>> script and breaks it. >>> Not a fan of modyfing WRKSRC "manually", we have patches and SUBST_CMD >>> for that. You'd simply patch LOCALBASE into the shebang and later do >>> >>> pre-configure: >>> ${SUBST_CMD} ${WRKSRC}/nlay >>> >>> I'm happy to import your latest tarball with that, OK anyone? > > Looks good to me, however I'd like us to stop importing ports using > GH_*. Upstream already uses publishes release assets: > > https://github.com/jarun/nnn/releases > > Could someone get in touch with them and ask them to publish proper > source tarballs? I did ask them to release the source code as a proper tarball three weeks ago and it does not seem likely to happen before the next release (1.8) which brings fixes regarding dependencies and portability issues. I will reiterate the request but would not count on proper release tarball for current version. best > > -- > jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE -- If you wish to live wisely, ignore sayings -- including this one.
Re: [New] nnn-1.7
Ping. On Wed, Mar 14, 2018 at 5:13 PM, Klemens Nanni <k...@openbsd.org> wrote: > On Wed, Mar 14, 2018 at 02:37:22AM +0100, Ljuba Nedeljkovic wrote: >> Please find attached updated port's tarball with suggested fixes. One >> deviation from kn's tarball is removal of `patches/patch-nlay` file and >> doing shebang fix using LOCALBASE with `post-extract` target. Said >> patch leaves literal `#!${LOCALBASE}/bin/bash` in installed `nlay` >> script and breaks it. > Not a fan of modyfing WRKSRC "manually", we have patches and SUBST_CMD > for that. You'd simply patch LOCALBASE into the shebang and later do > > pre-configure: > ${SUBST_CMD} ${WRKSRC}/nlay > > I'm happy to import your latest tarball with that, OK anyone? -- If you wish to live wisely, ignore sayings -- including this one.
Re: [New] nnn-1.7
Fixed as suggested. Thanks, -ljuba On 14.03, Klemens Nanni wrote: > On Wed, Mar 14, 2018 at 02:37:22AM +0100, Ljuba Nedeljkovic wrote: > > Please find attached updated port's tarball with suggested fixes. One > > deviation from kn's tarball is removal of `patches/patch-nlay` file and > > doing shebang fix using LOCALBASE with `post-extract` target. Said > > patch leaves literal `#!${LOCALBASE}/bin/bash` in installed `nlay` > > script and breaks it. > Not a fan of modyfing WRKSRC "manually", we have patches and SUBST_CMD > for that. You'd simply patch LOCALBASE into the shebang and later do > > pre-configure: > ${SUBST_CMD} ${WRKSRC}/nlay > > I'm happy to import your latest tarball with that, OK anyone? nnn-1.7.tar.gz Description: Binary data
Re: [New] nnn-1.7
Hello, Please find attached updated port's tarball with suggested fixes. One deviation from kn's tarball is removal of `patches/patch-nlay` file and doing shebang fix using LOCALBASE with `post-extract` target. Said patch leaves literal `#!${LOCALBASE}/bin/bash` in installed `nlay` script and breaks it. Thanks everyone for taking time to review and advise the work. Special thanks to kn@ for coaching and guidance that made this first attempt at porting software to OpenBSD pretty painless. Best, -ljuba On 13.03, Klemens Nanni wrote: > From: Klemens Nanni <k...@openbsd.org> > To: Ljuba Nedeljkovic <ljuba@gmail.com> > Cc: > Bcc: > Subject: Re: [New] nnn-1.7 > Reply-To: > In-Reply-To: <20180311203948.wqkdu5kxbhlrg...@lada.probisvet.io> > > On Sun, Mar 11, 2018 at 09:39:48PM +0100, Ljuba Nedeljkovic wrote: > > On 10.03, mitchell wodach wrote: > > > I get this error when I run "make test" > > > > > > openbsdcurrent# make test > > > ===> Regression tests for nnn-1.7 > > > gmake: *** No rule to make target 'test'. Stop. > > > *** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2777 > > > '/usr/ports/pobj/nnn-1.7/.test_done') > > > *** Error 1 in /usr/ports/myshit/sysutils/nnn > > > (/usr/ports/infrastructure/mk/bsd.port.mk:2419 'test') > > > > > > Try adding NO_TEST=Yes. to your Makefile > > > > Fixed. New tarball is attached to mail with most remarks. > Almost there. With GH_* set you can leave DISTNAME as described in > Makefile.template or bsd.port.mk(5) for that matter. > > See my attached tarball fixing this besides some whitespace issues and > other small nits; I've also taken care of the completion scripts. > > /usr/ports/infrastructure/bin/portcheck also tells if your port seems > fine, in that case it would warn you about an empty line in PLIST. nnn-1.7.tar.gz Description: Binary data
Re: [NEW] devel/py-intervaltree
Builds and installs on amd64, current, but `make test` fails with: ===> Regression tests for py-intervaltree-2.1.0 Version: 2.1.0 Reading README.rst running test running egg_info writing requirements to intervaltree.egg-info/requires.txt writing intervaltree.egg-info/PKG-INFO writing top-level names to intervaltree.egg-info/top_level.txt writing dependency_links to intervaltree.egg-info/dependency_links.txt reading manifest file 'intervaltree.egg-info/SOURCES.txt' reading manifest template 'MANIFEST.in' writing manifest file 'intervaltree.egg-info/SOURCES.txt' running build_ext = test session starts === platform openbsd6 -- Python 2.7.14, pytest-3.1.2, py-1.4.34, pluggy-0.4.0 rootdir: /usr/ports/pobj/py-intervaltree-2.1.0/intervaltree-2.1.0, inifile: setup.cfg collected 2 items / 3 errors ERRORS = ERROR collecting lib/intervaltree/interval.py __ /usr/local/lib/python2.7/site-packages/py/_path/local.py:680: in pyimport raise self.ImportMismatchError(modname, modfile, self) E ImportMismatchError: ('intervaltree.interval', '/usr/ports/pobj/py-intervaltree-2.1.0/intervaltree-2.1.0/intervaltree/interval.py', local('/usr/ports/pobj/py-intervaltree-2.1.0/intervaltree-2.1.0/lib/intervaltree/interval.py')) __ ERROR collecting lib/intervaltree/intervaltree.py /usr/local/lib/python2.7/site-packages/py/_path/local.py:680: in pyimport raise self.ImportMismatchError(modname, modfile, self) E ImportMismatchError: ('intervaltree.intervaltree', '/usr/ports/pobj/py-intervaltree-2.1.0/intervaltree-2.1.0/intervaltree/intervaltree.py', local('/usr/ports/pobj/py-intervaltree-2.1.0/intervaltree-2.1.0/lib/intervaltree/intervaltree.py')) __ ERROR collecting lib/intervaltree/node.py /usr/local/lib/python2.7/site-packages/py/_path/local.py:680: in pyimport raise self.ImportMismatchError(modname, modfile, self) E ImportMismatchError: ('intervaltree.node', '/usr/ports/pobj/py-intervaltree-2.1.0/intervaltree-2.1.0/intervaltree/node.py', local('/usr/ports/pobj/py-intervaltree-2.1.0/intervaltree-2.1.0/lib/intervaltree/node.py')) === warnings summary None [pytest] section in setup.cfg files is deprecated, use [tool:pytest] instead. -- Docs: http://doc.pytest.org/en/latest/warnings.html !!! Interrupted: 3 errors during collection ! = 1 warnings, 3 error in 0.31 seconds === *** Error 2 in . (/usr/ports/lang/python/python.port.mk:197 'do-test': @cd /usr/ports/pobj/py-intervaltree-2.1.0/intervaltree-2.1.0 && /usr/...) *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2771 '/usr/ports/pobj/py-intervaltree-2.1.0/.test_done') *** Error 1 in /usr/ports/mystuff/devel/py-intervaltree (/usr/ports/infrastructure/mk/bsd.port.mk:2419 'test') I did not test functioanlity of installed port and cannot tell if those failing tests are show stoppers. Cheers, -ljuba On 07.03, Remi Pointel wrote: > Hi, > > attached is the port of intervaltree, a dependency of floss. > > Ok? > > -- > $ pkg_info py-intervaltree > Information for inst:py-intervaltree-2.1.0 > > Comment: > editable interval tree data structure for Python 2 and 3 > > Required by: > py-viv_utils-0.3.9 > > Description: > A mutable, self-balancing interval tree for Python 2 and 3. Queries may > be by > point, by range overlap, or by range envelopment. This library was > designed to > allow tagging text and time intervals, where the intervals include the > lower > bound but not the upper bound. > > Maintainer: The OpenBSD ports mailing-list> > WWW: https://github.com/chaimleib/intervaltree > -- > > Cheers, > > Remi.
Re: [NEW] devel/py-funcy
OK on amd64m -current Cheers, -ljuba On 07.03, Remi Pointel wrote: > Hi, > > attached is the port of funcy: a fancy and practical functional tools. > > It's an indirect dependency of floss: > > -- > $ pkg_info py-funcy > Information for inst:py-funcy-1.10.1 > > Comment: > fancy and practical functional tools > > Required by: > py-viv_utils-0.3.9 > > Description: > A collection of fancy functional tools focused on practicality. > > Maintainer: The OpenBSD ports mailing-list> > WWW: https://github.com/Suor/funcy > -- > > Cheers, > > Remi.
Re: [NEW] devel/py-tabulate
OK on amd64, -current Cheers, -ljuba On 07.03, Remi Pointel wrote: > Hi, > > this is the port of py-tarbulate. > > Ok? > > --- > $ pkg_info py-tabulate > Information for inst:py-tabulate-0.8.2 > > Comment: > pretty-print tabular data > > Required by: > floss-1.5.0 > > Description: > Pretty-print tabular data in Python, a library and a command-line > utility. > The main use cases of the library are: > * printing small tables without hassle: just one function call, > formatting is guided by the data itself > * authoring tabular data for lightweight plain-text markup: multiple > output formats suitable for further editing or transformation > * readable presentation of mixed textual and numeric data: smart > column alignment, configurable number formatting, alignment by a > decimal point > > Maintainer: The OpenBSD ports mailing-list> > WWW: https://bitbucket.org/astanin/python-tabulate > > --- > > Cheers, > > Remi.
Re: Fwd: [NEW] security/floss
Hello, On freshly updated -current and /usr/ports, on amd64 `make test` fails with: ===> Returning to build of floss-1.5.0 ===> floss-1.5.0 depends on: py-plugnplay-* -> py-plugnplay-0.5.3 >> Broken dependency: security/py-viv_utils non existent \ (DEPENDS was security/py-viv_utils) in security/floss *** Error 1 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2073\ '/usr/ports/pobj/floss-1.5.0/.dep-securit `port-lib-depends-check` and `package` targets fail as well with the same complaint about missing dependency. Is `py-viv_utils` a port that is currently in development? Cheers On 12.03, Remi Pointel wrote: > > > Courriel original > Objet: [NEW] security/floss > Date: 10-03-2018 08:52 > De: Remi Pointel> À: The OpenBSD ports mailing-list > > Hi, > > attached is the port of floss: FireEye Labs Obfuscated String Solver. > > - > $ pkg_info floss > Information for inst:floss-1.5.0 > > Comment: > FireEye Labs Obfuscated String Solver > > Description: > The FireEye Labs Obfuscated String Solver (FLOSS) uses advanced static > analysis > techniques to automatically deobfuscate strings from malware binaries. You > can > use it just like strings.exe to enhance basic static analysis of unknown > binaries. > Rather than heavily protecting backdoors with hardcore packers, many malware > authors evade heuristic detections by obfuscating only key portions of an > executable. Often, these portions are strings and resources used to > configure > domains, files, and other artifacts of an infection. These key features will > not > show up as plaintext in output of the strings.exe utility that is commonly > used > during basic static analysis. > > Maintainer: Remi Pointel > > WWW: https://github.com/fireeye/flare-floss > - > > Ok? > > Cheers, > > Remi.
Re: [New] nnn-1.7
On 10.03, mitchell wodach wrote: > I get this error when I run "make test" > > openbsdcurrent# make test > ===> Regression tests for nnn-1.7 > gmake: *** No rule to make target 'test'. Stop. > *** Error 2 in . (/usr/ports/infrastructure/mk/bsd.port.mk:2777 > '/usr/ports/pobj/nnn-1.7/.test_done') > *** Error 1 in /usr/ports/myshit/sysutils/nnn > (/usr/ports/infrastructure/mk/bsd.port.mk:2419 'test') > > Try adding NO_TEST=Yes. to your Makefile Fixed. New tarball is attached to mail with most remarks. > > On Thu, Mar 8, 2018 at 10:49 AM, Ljuba Nedeljkovic <ljuba@gmail.com> > wrote: > > Hello, > > > > Attached is the port of nnn, "The missing terminal file browser for X" > > > > Apart from development machine (amd64) it was tested on clean base > > OpenBSD install also on amd64. Additional tests/comments/ok would be > > highly appreciated. > > > > Cheers, > > -ljuba
Re: [New] nnn-1.7
Thank you for taking time to look into this. On 10.03, mitchell wodach wrote: > change ncurses to curses in you WANTLIB. > > Mitch > Fixed > > On Sat, Mar 10, 2018 at 12:19 PM, Klemens Nanni <k...@openbsd.org> wrote: > > On Thu, Mar 08, 2018 at 05:49:51PM +0100, Ljuba Nedeljkovic wrote: > >> Attached is the port of nnn, "The missing terminal file browser for X" > >> > >> Apart from development machine (amd64) it was tested on clean base > >> OpenBSD install also on amd64. Additional tests/comments/ok would be > >> highly appreciated. > > COMMENT starts with an upper case letter. > > > > As a github project without proper release tarballs, please use GH_*. > > Can you communicate with upstream to provide stable release tarballs? > > They're already packaging for linux, so this shouldn't take much effort. > > > > The license marker is missing. > > > > WRK{DIST,SRC,BUILD} can go once GH_* is set. > > > > PLIST contains an empty line. > > > > Sources provide shell completions, what about packaging them as well? > > > > There is no need for patch-Makefile, you can pass these variables in > > various ways. > > > > For replacing the shebang please see LOCALBASE in bsd.port.mk(5). This > > also implies a missing RDEP on shells/bash. > > > > https://www.openbsd.org/faq/ports/guide.html is helpful in getting these > > fixed, but you can also look at other ports. > >
[New] nnn-1.7
Hello, Attached is the port of nnn, "The missing terminal file browser for X" Apart from development machine (amd64) it was tested on clean base OpenBSD install also on amd64. Additional tests/comments/ok would be highly appreciated. Cheers, -ljuba nnn-1.7.tar.gz Description: application/gzip
New port: sysutils/nnn
Hello, I'm about to get my hands a bit dirty with first stub at porting to OpenBSD with `nnn` (https://github.com/jarun/nnn). If someone is already working on it, please let me know. Also, sorry about previous half-baked email that went out by accident (ashamed). -ljuba
New port: sysutils/nnn
Hello, I'm about to get my hands a bit dirty with first stub at porting software to OpenBSD.