Anthony J. Bentley said:
> Not sure if this is related, but sound is very choppy for me, and:
>
> AV: 00:05:23 / 01:40:58 (5%) A-V: 0.020
> [ao/sndio] Blocking until remaining audio is played... (sndio design bug).
>
> was added in this commit:
> https://github.com/mpv-player/mpv/commit/387d5f55
"Dmitrij D. Czarkoff" writes:
> FWIW on my ThinkPad E325 the performance of mpv is really bad. (MPlayer
> does no good here either, although ffplay copes with everything just
> fine.) I also noticed that it has problems with unmuting if master
> output was muted before mpv started. To really unm
Ping again.
This has been tested on i386 and amd64.
Is there any interest?
On Nov 14, 2014, at 9:48 AM, Eric Lalonde wrote:
> Ping.
>
> On Nov 11, 2014, at 12:20 PM, Eric Lalonde wrote:
>>>
>>> Hi ports —
>>>
>>> Attached is a new port, graphics/ploticus.
>>> pkg/DESCR:
>>> Ploticus is a
Henrik Friedrichsen said:
> You have disabled libdvdnav and moved it to BUILD_DEPENDS. Was this
> intentional?
No, I disabled libdvdnav by mistake and moved it to BUILD_DEPENDS when
``make package'' said it wasn't needed in LIB_DEPENDS, as I was
mistakenly assuming that it was linked in statically
Thanks a lot for your changes. They all seem reasonable and help me
understanding how things are done in OpenBSD ports. Looking at existing
ports is not always ideal, as they often seem to do things differently
from how they should be done now.
On Thu, Nov 20, 2014 at 02:43:05AM +0100, Dmitrij D.
Henrik Friedrichsen said:
> I understand. I have attached another version that fetches all the files
> in the fetch phase.
>
> Could you give it another try?
I made some changes to the port. (See attached tarball for details.)
FWIW on my ThinkPad E325 the performance of mpv is really bad. (MPl
Hi
I'm away next week but I can make a release when I get back.
On Wed, Nov 19, 2014 at 01:27:38PM -0500, Bryan Steele wrote:
> On Tue, Nov 18, 2014 at 10:32:58PM +0100, Landry Breuil wrote:
> > On Tue, Nov 18, 2014 at 10:01:33PM +0100, frantisek holop wrote:
> > > Philip Guenther, 18 Nov 2014
On 2014/11/19 23:34, Mikolaj Kucharski wrote:
> I've tested below patch and results seems to be good:
>
>
> for i in www.secure.io www.secure.io:8443 www.amazon.com www.google.com
> www.facebook.com
> do
> for j in auto sslv2 sslv3 tlsv1 tlsv1_1 tlsv1_2 pfs
> do
> echo "===> wget -S -O /
I've tested below patch and results seems to be good:
for i in www.secure.io www.secure.io:8443 www.amazon.com www.google.com
www.facebook.com
do
for j in auto sslv2 sslv3 tlsv1 tlsv1_1 tlsv1_2 pfs
do
echo "===> wget -S -O /dev/null --progress dot:mega --secure-protocol $j
https://$i/ <
Mikolaj Kucharski writes:
> I can confirm that below diff, makes wget work on TLSv1.2-only site again.
Thanks for confirming.
So, here's a patch that makes wget use TLSv1+ instead of TLSv1.0 by
default - and with --secure-protocol=pfs - while making sure that we
don't accept SSLv[23].
Index: M
Hello Stuart,
Le 19/11/2014 00:16, Stuart Henderson a écrit :
> On 2014/11/18 22:01, Mxher wrote:
>> I'm using dibbler (http://klub.com.pl/dhcpv6/) so I made a port/package
>> for my own purpose (mostly because I wanted to try to build my own
>> packages).
>
> I've attached a port that's been sit
On Wed, Nov 19, 2014 at 10:00:18PM +0100, Donovan Watteau wrote:
> Hi,
>
> Now that bzip2 support has been enabled in devel/boost, let me
> present you archivers/innoextract.
>
> Inno Setup is a tool to create installers for Microsoft Windows
> applications. innoextract allows to extract such in
Hey,
On Wed, Nov 19, 2014 at 09:43:06PM +0100, Dmitrij D. Czarkoff wrote:
> This sounds very wrong. Also, systrace blocks this step. Consequently,
> port does not build.
I understand. I have attached another version that fetches all the files
in the fetch phase.
Could you give it another try?
Hi,
Now that bzip2 support has been enabled in devel/boost, let me
present you archivers/innoextract.
Inno Setup is a tool to create installers for Microsoft Windows
applications. innoextract allows to extract such installers under
non-windows systems without running the actual installer using W
Landry Breuil said:
> waf ? no fucking way. We got rid of that utter piece of crap for a
> reason
Could you please elaborate on this? You suggest custom Makefile in
ports? Or you suggest avoiding mpv because of its waf-based build
system? Or something else?
--
Dmitrij D. Czarkoff
Landry Breuil, 19 Nov 2014 21:30:
> On Wed, Nov 19, 2014 at 09:18:54PM +0100, frantisek holop wrote:
> > Henrik Friedrichsen, 19 Nov 2014 19:55:
> >
> > >
> > > On Thu, Nov 13, 2014 at 03:35:41AM +0100, Henrik Friedrichsen wrote:
> > > > Some notes:
> > > > - multimedia/libdvdnav is required
> >
Henrik Friedrichsen said:
> - Bootstrap and download the recommended waf with the script provided
This sounds very wrong. Also, systrace blocks this step. Consequently,
port does not build.
--
Dmitrij D. Czarkoff
I can confirm that below diff, makes wget work on TLSv1.2-only site again.
On Wed, Nov 19, 2014 at 09:04:55PM +0100, Jérémie Courr??ges-Anglas wrote:
> Index: patches/patch-src_openssl_c
> ===
> RCS file: /cvs/ports/net/wget/patches/
On Wed, Nov 19, 2014 at 09:18:54PM +0100, frantisek holop wrote:
> Henrik Friedrichsen, 19 Nov 2014 19:55:
>
> >
> > On Thu, Nov 13, 2014 at 03:35:41AM +0100, Henrik Friedrichsen wrote:
> > > Some notes:
> > > - multimedia/libdvdnav is required
> > > - You probably shouldn't hardcode /usr/local,
Henrik Friedrichsen, 19 Nov 2014 19:55:
>
> On Thu, Nov 13, 2014 at 03:35:41AM +0100, Henrik Friedrichsen wrote:
> > Some notes:
> > - multimedia/libdvdnav is required
> > - You probably shouldn't hardcode /usr/local, but instead use
> > ${LOCALBASE}
> > - During the initial check it says: Blur
Stuart Henderson writes:
> On 2014/11/19 08:16, Kent Fritz wrote:
>> Wget is only sending TLS 1.0 in client hello, and the server is
>> refusing. This seems to be a problem with the port, as wget 1.14 on
>> my Linux box sends a TLS 1.2 hello, as does wget on OpenBSD 5.4 (also
>> 1.14).
>
> This
"Martijn Rijkeboer" writes:
> Hi,
Hi,
> During the upgrade to 5.6 we've switched from Cfengine to Ansible. Therefore
> I would like to drop maintainership for sysutils/cfengine since we don't use
> it any more.
Done, thanks. Any takers?
--
jca | PGP: 0x1524E7EE / 5135 92C1 AD36 5293 2BDF D
Hi,
During the upgrade to 5.6 we've switched from Cfengine to Ansible. Therefore
I would like to drop maintainership for sysutils/cfengine since we don't use
it any more.
Kind regards,
Martijn Rijkeboer
Hey,
because I'd really like to see this port included and since the OP has
not responded so far, I took the liberty to work on the port.
On Thu, Nov 13, 2014 at 03:35:41AM +0100, Henrik Friedrichsen wrote:
> Some notes:
> - multimedia/libdvdnav is required
> - You probably shouldn't hardcode /us
On Tue, Nov 18, 2014 at 10:32:58PM +0100, Landry Breuil wrote:
> On Tue, Nov 18, 2014 at 10:01:33PM +0100, frantisek holop wrote:
> > Philip Guenther, 18 Nov 2014 12:42:
> > > Executive summary: delete the procmail port; the code is not safe and
> > > should not be used as a basis for any further
On 2014/11/19 16:38, Stuart Henderson wrote:
> On 2014/11/19 08:16, Kent Fritz wrote:
> > Wget is only sending TLS 1.0 in client hello, and the server is
> > refusing. This seems to be a problem with the port, as wget 1.14 on
> > my Linux box sends a TLS 1.2 hello, as does wget on OpenBSD 5.4 (al
On 2014/11/19 08:16, Kent Fritz wrote:
> Wget is only sending TLS 1.0 in client hello, and the server is
> refusing. This seems to be a problem with the port, as wget 1.14 on
> my Linux box sends a TLS 1.2 hello, as does wget on OpenBSD 5.4 (also
> 1.14).
This is fallout from our OPENSSL_VERSION
Wget is only sending TLS 1.0 in client hello, and the server is
refusing. This seems to be a problem with the port, as wget 1.14 on
my Linux box sends a TLS 1.2 hello, as does wget on OpenBSD 5.4 (also
1.14).
On Tue, Nov 18, 2014 at 10:31 PM, Mikolaj Kucharski
wrote:
> Hi,
>
> I didn't notice w
On 2014/11/19 09:14, sven falempin wrote:
> Porters,
>
> Did someone tried to work on that ?
>
> http://www.kamailio.org/dokuwiki/doku.php/packages:pkgs
Kamailio is in ports already. It is a bit of a different thing than
Asterisk though, think of it as more of a SIP message router, rather
than a
Porters,
Did someone tried to work on that ?
http://www.kamailio.org/dokuwiki/doku.php/packages:pkgs
( my sip provider want a bleeding edge version of asterisk with
specific register frequency,
so if you know how to change the register frequency in the in ports
asterisk you are welcome to answer
Hi Mikolaj,
Mikolaj Kucharski writes:
> On Wed, Nov 19, 2014 at 12:50:14AM +0100, Dmitrij D. Czarkoff wrote:
>> Mikolaj Kucharski said:
>> > Description:
>> > This is a powerful program at which you can throw a mess of unordered
>> ^^
>> Please, edit this away. It rea
Landry Breuil writes:
> On Tue, Nov 18, 2014 at 10:01:33PM +0100, frantisek holop wrote:
> > Philip Guenther, 18 Nov 2014 12:42:
> > > Executive summary: delete the procmail port; the code is not safe and
> > > should not be used as a basis for any further work.
> >
> > just for the record, what
On 2014/11/19 07:09, Stephane Tougard wrote:
> I do not even imagine my life without procmail, I use it since 20 years,
> it's kind of basic Unix tool, documented and used everywhere ...
>
> Is it not possible to find a new upstream maintainer for such an
> important piece of art than just try to
On 11/19/2014 03:47 AM, frantisek holop wrote:
> but even then, i think the port should not be removed.
> most of the software in ports has bugs, so what.
So what?
Well, for starters, procmail runs on the (rather large) POSIX family of
systems. It may not run on all members of the POSIX family,
On 11/19/2014 01:09 AM, Stephane Tougard wrote:
> I do not even imagine my life without procmail, I use it since 20 years,
> it's kind of basic Unix tool, documented and used everywhere ...
>
> Is it not possible to find a new upstream maintainer for such an
> important piece of art than just try
On 2014-11-18 Tue 22:01 PM |, frantisek holop wrote:
> Philip Guenther, 18 Nov 2014 12:42:
> > Executive summary: delete the procmail port; the code is not safe and
> > should not be used as a basis for any further work.
>
> just for the record, what is the alternative
> you would recommend?
>
Stefan Sperling, 19 Nov 2014 09:08:
> Code (no matter how old) riddled with security bugs should be removed
> if nobody steps up to fix them. Philip doesn't want to step up. I don't
> want to step up (I still use procmail at the moment but I'd rather look
> for better alternatives). You don't want
On Wed, Nov 19, 2014 at 07:09:28AM +0100, Stephane Tougard wrote:
> I do not even imagine my life without procmail, I use it since 20 years,
> it's kind of basic Unix tool, documented and used everywhere ...
>
> Is it not possible to find a new upstream maintainer for such an
> important piece of
38 matches
Mail list logo
