On Sun, Nov 03, 2019 at 08:50:05PM -0600, Lucas Raab wrote:
> On Sun, Nov 03, 2019 at 01:09:03PM -0800, Greg Steuck wrote:
> > On Sun, Nov 3, 2019 at 6:10 AM Lucas Raab wrote:
> > > > Lucas, have you tried using ykman?
> > >
> > > I have, using Python 3. The other dependencies/ports (py-fido2 and
On Sun, Nov 03, 2019 at 01:09:03PM -0800, Greg Steuck wrote:
> On Sun, Nov 3, 2019 at 6:10 AM Lucas Raab wrote:
> > > Lucas, have you tried using ykman?
> >
> > I have, using Python 3. The other dependencies/ports (py-fido2 and
> > pyscard) that I submitted are now Python 3 only as well due to pcs
On Sun, Nov 3, 2019, at 01:05, Stuart Henderson wrote:
> On 2019/10/21 13:12, Stuart Henderson wrote:
> > Reviewing libluv/luv again as asked by Edd, I got rather confused that
> > it installed libluv.so.0.0 in /usr/local/lib which isn't usable from Lua
> > (which would expect luv.so in /usr/local/
> On Nov 4, 2019, at 6:18 AM, Kurt Mosiejczuk wrote:
>
> On Sun, Nov 03, 2019 at 10:06:52PM +0100, Marc Espie wrote:
>> On Mon, Nov 04, 2019 at 02:32:03AM +0900, Daniel Dickman wrote:
clang doesn't error out, gcc does.
Why does numpy use gcc?
>
>>> Because that's what upstream reco
> On Nov 4, 2019, at 6:06 AM, Marc Espie wrote:
>
> On Mon, Nov 04, 2019 at 02:32:03AM +0900, Daniel Dickman wrote:
>>> clang doesn't error out, gcc does.
>>> Why does numpy use gcc?
>>
>> Because that’s what upstream recommends in their docs.
>>
>> “Note that NumPy is developed mainly usin
On Sun, Nov 03 2019, Marc Espie wrote:
> On Mon, Nov 04, 2019 at 02:32:03AM +0900, Daniel Dickman wrote:
>> > clang doesn't error out, gcc does.
>> > Why does numpy use gcc?
>>
>> Because that’s what upstream recommends in their docs.
>>
>> “Note that NumPy is developed mainly using GNU compiler
On Sun, Nov 3, 2019 at 6:10 AM Lucas Raab wrote:
> > Lucas, have you tried using ykman?
>
> I have, using Python 3. The other dependencies/ports (py-fido2 and
> pyscard) that I submitted are now Python 3 only as well due to pcsclite
> now being a Python 3-only package.
Unfortunately I'm still uns
On Mon, Nov 04, 2019 at 02:32:03AM +0900, Daniel Dickman wrote:
> > clang doesn't error out, gcc does.
> > Why does numpy use gcc?
>
> Because that’s what upstream recommends in their docs.
>
> “Note that NumPy is developed mainly using GNU compilers. Compilers from
> other vendors such as Intel
On Thu, Oct 24, 2019 at 07:04:42AM +, wen heping wrote:
> Hi, ports@:
>
>Here is a simple patch for www/p5-Dancer2-Plugin-DBIC:
> i) Update to 0.0100
> ii) Remove a whitespace in DESCR
>It is required by the future update of p5-Dancer2.
>
>It build well and pass all test
* Edd Barrett wrote:
> On Sun, Oct 20, 2019 at 10:37:48AM +0100, Edd Barrett wrote:
> > On Sun, Oct 20, 2019 at 10:35:05AM +0100, Edd Barrett wrote:
> > > Attached is a mega-diff to update TeX Live.
> >
> > Forgot to say: I've tested this with a partial bulk on yesterday's
> > snapshot. No issues
On Fri, Oct 04, 2019 at 01:44:10PM +0200, Klemens Nanni wrote:
> rsadowski noted that DESCR is too lenghty and upon second read I agree
> that my shameless dump of the project's README is too much.
>
> Nonetheless I'd like to provide more information than
>
> yq is a command line processor
This is another simple maintainer update of lowdown from 0.4.3 to 0.4.6.
The changes included in this release are:
lowdown 0.4.4: "In CommonMark mode, have the first ordered list item be
output as the initial list value. This differs from regular MarkDown,
which always starts lists at one. Also br
On Thu 31/10/2019 12:53, Nam Nguyen wrote:
>
> net/dnscrypt-proxy 2.0.31 was just released to fix two regressions on
> October 31, 2019. The diff is pasted below.
Diff looks good, and update runs ok on amd64. OK bket@.
I will commit this update tomorrow...unless someone beats me to it.
On 2019/11/03 10:29, Lucas Raab wrote:
> On Fri, Nov 01, 2019 at 09:07:31PM +0100, Klemens Nanni wrote:
> > On Fri, Nov 01, 2019 at 02:44:02PM -0500, Lucas Raab wrote:
> > > Updated to make it Python 3 only since the pcsc-lite depends is Python
> > > 3 only
> > PKGNAME should MODPY_PY_PREFIX instea
This is another simple maintainer update of sblg from 0.5.7 to 0.5.8.
The changes included in this release are:
sblg 0.5.8: "Add data-sblg-const-img variants of the existing
data-sblg-img and friends. This behaves like implicitly grabbing from
the first in that only the first invocation sets the
Now that the python issues seem to be solved, just one comment on the proposed
diff:
> -MODFORTRAN_COMPILER =gfortran
> +MODFORTRAN_COMPILER =flang
numpy developers basically say to use gnu compilers, otherwise you’re on your
own.
And numpy’s fortran compiler can’t be switched in isola
> clang doesn't error out, gcc does.
> Why does numpy use gcc?
Because that’s what upstream recommends in their docs.
“Note that NumPy is developed mainly using GNU compilers. Compilers from other
vendors such as Intel, Absoft, Sun, NAG, Compaq, Vast, Portland, Lahey, HP,
IBM, Microsoft are onl
> My PRs have all been merged, so here's an updated port that uses
> the Yubico upstream instead of my fork.
This port works for me. I successfully ssh-d into my localhost with a
newly enrolled
key:
Nov 3 09:13:57 hippy sshd[18160]: Accepted publickey for greg from
127.0.0.1 port 4508 ssh2: ECDS
bulk build on arm64.ports.openbsd.org
started on Sat Nov 2 02:57:25 MDT 2019
finished at Sun Nov 3 10:01:01 MST 2019
lasted 1D08h03m
done with kern.version=OpenBSD 6.6-current (GENERIC.MP) #300: Fri Nov 1
14:04:24 MDT 2019
built packages:9614
Nov 2:5751
Nov 3:3862
critical path missing pkgs:
On Fri, Nov 01, 2019 at 09:07:31PM +0100, Klemens Nanni wrote:
> On Fri, Nov 01, 2019 at 02:44:02PM -0500, Lucas Raab wrote:
> > Updated to make it Python 3 only since the pcsc-lite depends is Python
> > 3 only
> PKGNAME should MODPY_PY_PREFIX instead of "py-".
>
> DESCR should be a proper sentenc
Hi,
update to poppler-0.82.0.
libpoppler-cpp.so needs a major bump due to symbol removals, which
is missing in the upstream version.
I'm currently running a bulk build with this on amd64, which will
take a little bit.
As always, tests from other people (and on other architectures) are
welcome.
On Sun, Nov 03 2019, Jeremie Courreges-Anglas wrote:
> Works for me on my laptop since yesterday. I plan to commit this
> tomorrow. ok?
This is an update to openvpn-2.4.8, not 2.4.28. Let's blame it on the
consciousness-altering cheese kindly provided by Miod. :)
--
jca | PGP : 0x1524E7EE /
Works for me on my laptop since yesterday. I plan to commit this
tomorrow. ok?
Index: Makefile
===
RCS file: /cvs/ports/net/openvpn/Makefile,v
retrieving revision 1.96
diff -u -p -r1.96 Makefile
--- Makefile22 Jun 2019 22:44:
On Fri, Oct 18 2019, Charlene Wendling wrote:
> On Thu, 17 Oct 2019 21:21:14 +0100
> Stuart Henderson wrote:
>
>> On 2019/10/17 10:01, Henry Jensen wrote:
>> > On Wed, 16 Oct 2019 16:07:34 +0100
>> > Stuart Henderson wrote:
>> >
>> > > On 2019/10/16 09:04, Henry Jensen wrote:
>> > > > Ping
>> >
On Sun, Nov 03, 2019 at 02:22:19PM +, Stuart Henderson wrote:
> I think both should be left, FreeBSD doesn't have HW_PHYSMEM64.
I see, thanks. Just looked and as presumed NetBSD has PHYSMEM64 while
Dragonfly does not just like FreeBSD, so the seems fine as is.
On Sun, Nov 03 2019, Stuart Henderson wrote:
> On 2019/11/03 14:57, Klemens Nanni wrote:
>> On Sun, Nov 03, 2019 at 12:17:13PM +0100, Jeremie Courreges-Anglas wrote:
>> > I'm sitting on a few changes in devel/git since some time already.
>> Thanks, I never noticed these until now.
>>
>> > - nghtt
On 2019/11/03 14:57, Klemens Nanni wrote:
> On Sun, Nov 03, 2019 at 12:17:13PM +0100, Jeremie Courreges-Anglas wrote:
> > I'm sitting on a few changes in devel/git since some time already.
> Thanks, I never noticed these until now.
>
> > - nghttp2 should not be listed here IMO. It really is a dep
On Sat, Nov 02, 2019 at 05:15:33PM -0700, Greg Steuck wrote:
> I installed a few ports to get all the way to /usr/local/bin/ykman and
> tried to run it on amd64-current-ish. It appears the py-fido2 port
> needs a bit more work. There is some OS sniffing code which seems to
> be missing any support
On Sat, Nov 02, 2019 at 05:15:33PM -0700, Greg Steuck wrote:
> I installed a few ports to get all the way to /usr/local/bin/ykman and
> tried to run it on amd64-current-ish. It appears the py-fido2 port
> needs a bit more work. There is some OS sniffing code which seems to
> be missing any support
On Sun, Nov 03, 2019 at 12:17:13PM +0100, Jeremie Courreges-Anglas wrote:
> I'm sitting on a few changes in devel/git since some time already.
Thanks, I never noticed these until now.
> - nghttp2 should not be listed here IMO. It really is a dep of libcurl,
> git itself doesn't use directly the
On Fri, 1 Nov 2019 15:41:50 +
Edd Barrett wrote:
> On Sun, Oct 20, 2019 at 10:37:48AM +0100, Edd Barrett wrote:
> > On Sun, Oct 20, 2019 at 10:35:05AM +0100, Edd Barrett wrote:
> > > Attached is a mega-diff to update TeX Live.
> >
> > Forgot to say: I've tested this with a partial bulk on yes
On Sun, 03 Nov 2019 12:44:31 +0100
Jeremie Courreges-Anglas wrote:
> On Fri, Oct 18 2019, Charlene Wendling wrote:
> > On Thu, 17 Oct 2019 21:21:14 +0100
> > Stuart Henderson wrote:
> >
> >> On 2019/10/17 10:01, Henry Jensen wrote:
> >> > On Wed, 16 Oct 2019 16:07:34 +0100
> >> > Stuart Henderson
On 2019/11/03 21:29, Damien Miller wrote:
> On Sun, 3 Nov 2019, Stuart Henderson wrote:
>
> > On 2019/11/03 00:14, Stuart Henderson wrote:
> > >
> > > Here are some small tweaks. Indicate in the package name that it's a
> > > post-release snapshot, set NO_TEST, start shared lib version at 0.0.
>
I'm sitting on a few changes in devel/git since some time already.
- nghttp2 should not be listed here IMO. It really is a dep of libcurl,
git itself doesn't use directly the nghttp API.
- sysctl(HW_PHYSMEM) wants an int. That doesn't work well if you have
a decent amount or ram. What d
On Sun, 3 Nov 2019, Stuart Henderson wrote:
> On 2019/11/03 00:14, Stuart Henderson wrote:
> >
> > Here are some small tweaks. Indicate in the package name that it's a
> > post-release snapshot, set NO_TEST, start shared lib version at 0.0.
> > This one is OK with me. Nice work with the HID drive
On 2019/11/03 00:14, Stuart Henderson wrote:
>
> Here are some small tweaks. Indicate in the package name that it's a
> post-release snapshot, set NO_TEST, start shared lib version at 0.0.
> This one is OK with me. Nice work with the HID driver! That was my
> main sticking point when I tried to ge
Ok with the REVISION bump.
--
Sent from a phone, apologies for poor formatting.
On 2 November 2019 22:49:21 Kurt Mosiejczuk wrote:
On Sat, Nov 02, 2019 at 10:16:03PM +0100, Jeremie Courreges-Anglas wrote:
To stay on the safe side, here's a simple diff for lang/python/2.7 which
unbreaks nump
On Fri, Nov 01, 2019 at 03:41:50PM +, Edd Barrett wrote:
> On Sun, Oct 20, 2019 at 10:37:48AM +0100, Edd Barrett wrote:
> > On Sun, Oct 20, 2019 at 10:35:05AM +0100, Edd Barrett wrote:
> > > Attached is a mega-diff to update TeX Live.
> >
> > Forgot to say: I've tested this with a partial bulk
On 2019/11/01 14:56, Lucas Raab wrote:
> On Thu, Oct 31, 2019 at 09:33:11PM +0100, Klemens Nanni wrote:
> > On Sun, Oct 27, 2019 at 04:37:42PM -0400, Kurt Mosiejczuk wrote:
> > > With these changes, OK kmos@
> > Looks good, a few things:
> >
> > Not sure how this library fits into sysutils as seco
On 2019/11/03 08:26, Stuart Henderson wrote:
> I'd just drop thd second category, devel is rwally "ports to help
> woth software development, plus random things where we ckuldn't find
> a better category". It doesn't make ot any easier to find this.
Bleh, sorry about the phone keyboard typos!
On 2019/11/02 14:31, Travis Cole wrote:
> Why not use the libluv port with Stuart's improvements?
>From my earlier mail,
On 2019/10/21 13:12, Stuart Henderson wrote:
> Reviewing libluv/luv again as asked by Edd, I got rather confused that
> it installed libluv.so.0.0 in /usr/local/lib which isn't
On 2019/11/02 10:40, Daniel Dickman wrote:
>
>
> > On Nov 2, 2019, at 10:33 AM, Kurt Mosiejczuk wrote:
> >
> > On Sat, Nov 02, 2019 at 07:03:57AM -0400, Daniel Dickman wrote:
> >
> On Nov 2, 2019, at 2:56 AM, Kurt Mosiejczuk wrote:
> >>
> 'So the existing py-numpy is unhappy with
42 matches
Mail list logo