As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. One common problem is
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. One common problem is
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles. Often,
these ports are so marked due to security concerns, such as known
exploits.
An overview of each port, inclu
As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness. Often,
this is due to a better alternative having become available and/or
the cessation of development on th
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Jeremie Le Hen wrote:
> Actually, I've just realized that I fixed net/unison232 in my local tree :o).
>
> Would you mind submitting it and applying the same for unison240?
>
> Here is the patch:
>
> Index: Makefile
> ===
> --- Makefile
On 03/21/15 11:49, Michelle Sullivan wrote:
> Jeremie Le Hen wrote:
>> Actually, I've just realized that I fixed net/unison232 in my local tree :o).
>>
>> Would you mind submitting it and applying the same for unison240?
>>
>> Here is the patch:
>>
>> Index: Makefile
>>
Guido Falsi wrote:
> On 03/21/15 11:49, Michelle Sullivan wrote:
>
>> Jeremie Le Hen wrote:
>>
>>> Actually, I've just realized that I fixed net/unison232 in my local tree
>>> :o).
>>>
>>> Would you mind submitting it and applying the same for unison240?
>>>
>>> Here is the patch:
>>>
>>>
Hi there,
how can I lock the screen by keystroke or button?
On my FreeBSD machine that can be achieved by pressing Win-l or by
choosing a button in the shutdown menu on the top right.
On this PC-BSD machine I can't find a method to achieve this :-)
Best regards
Gerrit
---\nPBI Informati
On 03/21/15 13:26, Michelle Sullivan wrote:
> Guido Falsi wrote:
>> On 03/21/15 11:49, Michelle Sullivan wrote:
>>
>>> Jeremie Le Hen wrote:
>>>
Actually, I've just realized that I fixed net/unison232 in my local tree
:o).
Would you mind submitting it and applying the s
Gerrit wrote:
> how can I lock the screen by keystroke or button?
That has nothing to do with FreeBSD. Or even with PC-BSD, for that matter.
It's part of the configuration of whatever window manager and/or desktop
environment you're using.
AvW
--
I'm not completely useless, I can be used as a
Guido Falsi wrote:
> On 03/21/15 13:26, Michelle Sullivan wrote:
>
>> Guido Falsi wrote:
>>
>>> On 03/21/15 11:49, Michelle Sullivan wrote:
>>>
>>>
Jeremie Le Hen wrote:
> Actually, I've just realized that I fixed net/unison232 in my local tree
>>
Hi,
on two different FreeBSD systems I'm getting build this port with
%%ETCSSH%% variable.
Isn't some kind of bug maybe ?
Example from rc.d script - openssh :
if [ -f %%ETCSSH%%/ssh_host_key -a \
-f %%ETCSSH%%/ssh_host_dsa_key -a \
-f %%ETCSSH%%/ssh_host_rsa_key
On 03/21/15 14:50, Michelle Sullivan wrote:
> Guido Falsi wrote:
>> On 03/21/15 13:26, Michelle Sullivan wrote:
>>
>>
>> This leads me to think there is some misalignment of the X11 option in
>> your setup, that's why I asked for the full log of the failed build, I
>> need to check the environme
> On 21.03.2015, at 15:50, Guido Falsi wrote:
> On 03/21/15 14:50, Michelle Sullivan wrote:
>> Which means that if unsetting X11 on in the port and not globally ocaml
>> is built with X11 and unison without - which poudriere will fail on when
>> it tries to find the dependencies... which means
On 03/20/15 01:11, Geoffrey Mainland wrote:
> On 03/17/2015 07:25 AM, Guido Falsi wrote:
>> On 03/17/15 11:44, Jeremie Le Hen wrote:
>>> On Tue, Mar 17, 2015 at 10:46 AM, Guido Falsi wrote:
On 03/17/15 09:31, Jeremie Le Hen wrote:
> On Mon, Mar 16, 2015 at 11:12 PM, Guido Falsi
> wr
On 3/21/15 10:41 AM, Guido Falsi wrote:
> On 03/20/15 01:11, Geoffrey Mainland wrote:
>> On 03/17/2015 07:25 AM, Guido Falsi wrote:
>>> On 03/17/15 11:44, Jeremie Le Hen wrote:
On Tue, Mar 17, 2015 at 10:46 AM, Guido Falsi wrote:
> On 03/17/15 09:31, Jeremie Le Hen wrote:
>> On Mon, M
On 03/21/15 18:58, Geoffrey Mainland wrote:
> On 3/21/15 10:41 AM, Guido Falsi wrote:
>> On 03/20/15 01:11, Geoffrey Mainland wrote:
>>> On 03/17/2015 07:25 AM, Guido Falsi wrote:
On 03/17/15 11:44, Jeremie Le Hen wrote:
> On Tue, Mar 17, 2015 at 10:46 AM, Guido Falsi
> wrote:
>>
On 03/21/15 17:55, Michael Grimm wrote:
>
>> On 21.03.2015, at 15:50, Guido Falsi wrote:
>> On 03/21/15 14:50, Michelle Sullivan wrote:
>
>
>>> Which means that if unsetting X11 on in the port and not globally ocaml
>>> is built with X11 and unison without - which poudriere will fail on when
>>
On 3/21/15 9:22 AM, "Ing. Břetislav Kubesa" wrote:
Hi,
on two different FreeBSD systems I'm getting build this port with
%%ETCSSH%% variable.
Isn't some kind of bug maybe ?
Example from rc.d script - openssh :
if [ -f %%ETCSSH%%/ssh_host_key -a \
-f %%ETCSSH%%/ssh_host_dsa
No problem at all, thank you :-)
Dne so 21. 3. 2015 20:28 uživatel Bryan Drewery
napsal:
> On 3/21/15 9:22 AM, "Ing. Břetislav Kubesa" wrote:
> > Hi,
> >
> > on two different FreeBSD systems I'm getting build this port with
> > %%ETCSSH%% variable.
> > Isn't some kind of bug maybe ?
> >
> > Exam
On 21.03.2015, at 19:10, Guido Falsi wrote:
> On 03/21/15 17:55, Michael Grimm wrote:
>> I recently (after last upgrade of poudriere-devel, although I do not know if
>> that is the cause) ran into a comparable issue with unison without X11 :
>>
>> | MWN> cat /usr/local/etc/poudriere.d/stab
On Fri, Mar 20, 2015 at 04:37:13PM +0100, Baptiste Daroussin wrote:
> Hi all,
>
> Some of you may have notice some work on the font area.
>
> The goal of this work is to prevent every single font package to act
> differently
> and most of the time not correctly.
>
> The change will be done in m
Basic context:
[I'm using an example taken from buildworld activity just for illustration.
Yes, I know that powerpc64 buildworld via clang is not yet supported.
buildworld is not the actual point here but does illustrate a pre-existing
build environment having the issue in question.]
> # freebs
Guido Falsi wrote:
>
> Exactly.
>
> There are four cases:
>
> one asks for both with or without X11, works fine, in both.
>
This is all ok.
> one asks for ocaml without X11 and unison with X11, this is wrong and
> cannot obviously work.
>
Absolutely. But this in theory should disable X11 i
Hello,
I'm having a problem with the port "handbrake".
>From the Makefile:
# Created by: Andrew Thompson
# $FreeBSD: head/multimedia/handbrake/Makefile 374303 2014-12-08 16:48:38Z
tijl $
The build and install of the port succeeds, but the resulting installation
is broken. Attempting to read a D
On Mar 21, 2015 8:21 PM, "Matt Klein" wrote:
>
> Hello,
>
> I'm having a problem with the port "handbrake".
>
> From the Makefile:
> # Created by: Andrew Thompson
> # $FreeBSD: head/multimedia/handbrake/Makefile 374303 2014-12-08 16:48:38Z
> tijl $
>
> The build and install of the port succeeds,
ports-mgmt/portell can't be installed now because its SourceForge project has
disappeared. It looks like the author is now just using a GitHub Gist for it:
https://gist.github.com/rkulla/1122022
Is that usable?
___
freebsd-ports@freebsd.org mailing lis
Hello,
Since FreeBSD now has Clang and always had its own shell, a lot of
dependencies and options like bash, gnu, hal, gcc, and gtk aren't
needed for many ports to compile. Some programs (especially gtk
affiliated and linux emulation programs) still fail without gmake, but
there
30 matches
Mail list logo
