On 28/10/2015 5:27 AM, Brooks Davis wrote:
> On Tue, Oct 27, 2015 at 11:03:07AM +, loic.b...@unix-experience.fr wrote:
>> Any news for this problem ?
>
> Upstream does not yet support python 3 so it remain broken. I've not
> yet had time to see if I can force the use of 2.7 when building. Si
On 28/10/2015 4:05 PM, sor...@cydem.org wrote:
>
> Howdy!
>
> I have a suggestion: to significantly speedup the packaging phase
> when installing ports, pass '-f tgz' flag to `pkg create`:
>--- Mk/bsd.commands.mk (revision 400371)
>+++ Mk/bsd.commands.mk (working copy)
>@@ -126,7
Howdy!
I have a suggestion: to significantly speedup the packaging phase
when installing ports, pass '-f tgz' flag to `pkg create`:
--- Mk/bsd.commands.mk (revision 400371)
+++ Mk/bsd.commands.mk (working copy)
@@ -126,7 +126,7 @@
PKG_DELETE?= ${PKG_BIN} delete -y
P
Hiya! A acquaintance of mine gave me your contact.
He was confident you would be very much interested to read my resume.
After browsing your homepage and seeing what it is you guys do, I'm also quite
sure
you will not be disappointed. I'm attaching my resume for you to go through.
I am very muc
On Tue, Oct 27, 2015 at 04:37:58PM +0100 I heard the voice of
A.J. "Fonz" van Werven, and lo! it spake thus:
>
> That I understand, but I'd expect that now with PHP 5.6 being the
> default, lang/php5 would point to lang/php56 instead of lang/php54,
There IS no lang/php54, and never has been. lan
On Tue, Oct 27, 2015 at 11:03:07AM +, loic.b...@unix-experience.fr wrote:
> Any news for this problem ?
Upstream does not yet support python 3 so it remain broken. I've not
yet had time to see if I can force the use of 2.7 when building. Simple
changes haven't worked. You can work around th
A.J. "Fonz" van Werven wrote on 10/27/2015 16:37:
Miroslav Lachman wrote:
It is right, because previously there was only one (moving target) port
"lang/php5" and no php51, php52, php53. Then this was changed to support
more than one version of PHP and lang/php5 is leftover from the past era.
Thank you very much, Kurt!
27.10.2015 19:50 пользователь "Kurt Jaeger" написал:
> Hi!
>
> > Could someone please commit changed described in
> > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203660 ?
>
> Done.
>
> --
> p...@opsec.eu+49 171 3101372 5 years t
Hi!
> Could someone please commit changed described in
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203660 ?
Done.
--
p...@opsec.eu+49 171 3101372 5 years to go !
___
freebsd-ports@freebsd.org mailing list
ht
Kubilay Kocak wrote:
> The real question that informs the decision is: Might/Do the people
> using the quarterly want/need this?
[snip]
> A really way to get a better feel is to browse the quarterly commit log:
>
> https://svnweb.freebsd.org/ports/branches/2015Q4/?view=log
>
> However, if you'r
On 28/10/2015 1:43 AM, A.J. "Fonz" van Werven wrote:
> Kubilay Kocak wrote:
>
>> Set merge-quarterly to ? in the bugzilla issue report, and ask (in a
>> comment) for the committer who resolved it in ports HEAD to kindly merge
>> it :)
>
> Thanks to you and Kurt Jaeger for the help. The committer
Miroslav Lachman wrote:
> It is right, because previously there was only one (moving target) port
> "lang/php5" and no php51, php52, php53. Then this was changed to support
> more than one version of PHP and lang/php5 is leftover from the past era.
That I understand, but I'd expect that now with
A.J. "Fonz" van Werven wrote on 10/27/2015 15:38:
Kurt Jaeger wrote:
[...]
There's one other thing I noticed, though. According to UPDATING entry
20150220, 5.6 is now the default PHP version. However, lang/php5 still
seems to point to to lang/php54. Trying to build lang/php5 (e.g.
"portmaster
Kubilay Kocak wrote:
> Set merge-quarterly to ? in the bugzilla issue report, and ask (in a
> comment) for the committer who resolved it in ports HEAD to kindly merge
> it :)
Thanks to you and Kurt Jaeger for the help. The committer in question has
now reassigned it to the security team so I'll w
Kurt Jaeger wrote:
> Is there an application that does not cope with newer versions of PHP ?
A quick survey on Freshports reveals:
- 651 ports build-/lib-/run-depending explicitly on *php56*;
- 67 ports build-/lib-/run-depending explicitly on *php55*;
- 0 ports build-/lib-/run-depending exp
Greetings!
Could someone please commit changed described in
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203660 ?
Thanks a lot!
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send a
On Oct 27, 2015 7:19 AM, "Kurt Jaeger" wrote:
>
> Hi!
>
> > Checking for packages with security vulnerabilities:
> > Database fetched: Mon Oct 26 00:09:27 CET 2015
> > php5-phar-5.4.45
> >
> > Can you tell when we can expect the update of this port?
>
> Is there an application that does not cope w
Hi!
> Checking for packages with security vulnerabilities:
> Database fetched: Mon Oct 26 00:09:27 CET 2015
> php5-phar-5.4.45
>
> Can you tell when we can expect the update of this port?
Is there an application that does not cope with newer versions of PHP ?
--
p...@opsec.eu+49
Any news for this problem ?
12 octobre 2015 19:50 "Brooks Davis" a écrit:
> On Fri, Oct 09, 2015 at 04:38:57PM +0200, Walter Schwarzenfeld wrote:
>
>> Can't test the patch in the above link, cause the port ignores python
>> 3.4 and I don't want deinstall python 2.7.
>
> I've figured out how to
Hello Jos,
Checking for packages with security vulnerabilities:
Database fetched: Mon Oct 26 00:09:27 CET 2015
php5-phar-5.4.45
Can you tell when we can expect the update of this port?
Surely the answer will be never, because PHP 5.4 has reached its end of
life.
You should switch to PHP 5.
Hi,
I've posted this on gmane, but am not sure it reached the list.
I've had the same problem and found the solution as follows:
1) skype was actually talking about libpulse-mainloop-glib.so.0 in the
/compat/linux installation, not in /usr/local.2) The solution was to manually
extract pulseaudio-
The Stupid One wrote:
> PHP 5.4 and related ports are set to expire on Jan 15 2015
That should be 2016, obviously. I guess my signature is quite appropriate.
AvW
--
I'm not completely useless, I can be used as a bad example.
signature.asc
Description: PGP signature
Jos Chrispijn wrote:
> Dear port maintainer,
You're aware that is not an actual person, right? It's
the general-purpose ports mailing list. When is
mentioned as a port's maintainer, that means the port in question doesn't
(currently) have a maintainer.
Moreover, the port you mention does have
Dear port maintainer,
Checking for packages with security vulnerabilities:
Database fetched: Mon Oct 26 00:09:27 CET 2015
php5-phar-5.4.45
Can you tell when we can expect the update of this port?
Thanks,
Jos Chrispijn
___
freebsd-ports@freebsd.o
Hello Kris,
Doesn't seem like we have had much response on the matter.
I would really be interested in starting this port. I don't mind the
coding from scratch, it would be fun for me.
If no one has any objection I can get started.
Go for it. :)
If you need any help feel free to ask. I als
25 matches
Mail list logo
