Hi,
CCd eadler@ as he did last commit.
When I'm trying update x11/xbitmaps x11/xtrans and other xorg-related(?)
ports I got:
===> License not correctly defined: for unknown licenses, defining
LICENSE_PERMS is mandatory (otherwise use a known LICENSE)
with DISABLE_LICENSES all works fine, sur
Sergey V. Dyatko wrote on 20.09.2011 11:06:
Hi,
CCd eadler@ as he did last commit.
When I'm trying update x11/xbitmaps x11/xtrans and other xorg-related(?)
ports I got:
===> License not correctly defined: for unknown licenses, defining
LICENSE_PERMS is mandatory (otherwise use a known LICEN
On Tue, 20 Sep 2011 11:42:17 +0400
Ruslan Mahmatkhanov wrote:
> Sergey V. Dyatko wrote on 20.09.2011 11:06:
> > Hi,
> >
> > CCd eadler@ as he did last commit.
> >
> > When I'm trying update x11/xbitmaps x11/xtrans and other
> > xorg-related(?) ports I got:
> >
> > ===> License not correctly de
On Tue, Sep 20, 2011 at 11:13:38AM +0300, Sergey V. Dyatko wrote:
> On Tue, 20 Sep 2011 11:42:17 +0400
> Ruslan Mahmatkhanov wrote:
>
> > Sergey V. Dyatko wrote on 20.09.2011 11:06:
> > > Hi,
> > >
> > > CCd eadler@ as he did last commit.
> > >
> > > When I'm trying update x11/xbitmaps x11/xtrans
> Hey everyone, I maintain devel/doxygen (sorry I didn't add my 2 cents
> earlier, I've been a bit busy) and was looking at this particular thread. I
> know someone filed a PR regarding the circular dependency, stating that it
> might be best to split apart doxygen so one port builds just the prog
Checked UPDATING and there isn't any mention. I get:
x11/xbitmaps # make
===> Vulnerability check disabled, database not found
===> License not correctly defined: for unknown licenses, defining
LICENSE_PERMS is mandatory (otherwise use a known LICENSE)
*** Error code 1
Stop in /usr/ports/x11/x
On 20 Sep 2011 13:10, "Edwin L. Culp W." wrote:
>
> Checked UPDATING and there isn't any mention. I get:
>
> x11/xbitmaps # make
> ===> Vulnerability check disabled, database not found
> ===> License not correctly defined: for unknown licenses, defining
> LICENSE_PERMS is mandatory (otherwise u
On Sep 20, 2011, at 4:23 AM, Baptiste Daroussin wrote:
> On Tue, Sep 20, 2011 at 11:13:38AM +0300, Sergey V. Dyatko wrote:
>> On Tue, 20 Sep 2011 11:42:17 +0400
>> Ruslan Mahmatkhanov wrote:
>>
>>> Sergey V. Dyatko wrote on 20.09.2011 11:06:
Hi,
CCd eadler@ as he did last commit
Sahil Tandon wrote on 20.09.2011 16:41:
On Sep 20, 2011, at 4:23 AM, Baptiste Daroussin wrote:
On Tue, Sep 20, 2011 at 11:13:38AM +0300, Sergey V. Dyatko wrote:
On Tue, 20 Sep 2011 11:42:17 +0400
Ruslan Mahmatkhanov wrote:
Sergey V. Dyatko wrote on 20.09.2011 11:06:
Hi,
CCd eadler@ as he
On Tue, Sep 20, 2011 at 7:13 AM, Chris Rees wrote:
>
> On 20 Sep 2011 13:10, "Edwin L. Culp W." wrote:
>>
>> Checked UPDATING and there isn't any mention. I get:
>>
>> x11/xbitmaps # make
>> ===> Vulnerability check disabled, database not found
>> ===> License not correctly defined: for unknow
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. The most common probl
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. The most common probl
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 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
15 matches
Mail list logo