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 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 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 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
Dear port maintainer,
The portscout new distfile checker has detected that one or more of your
ports appears to be out of date. Please take the opportunity to check
each of the ports listed below, and if possible and appropriate,
submit/commit an update. If any ports have already been updated, you
Marco Steinbach wrote on 20.06.2014 02:06:
Marco Steinbach wrote on 19.06.2014 23:49:
Miroslav Lachman schrieb:
I don't need DOCS, EXAMPLES etc. for each port as I normaly do not
use them on servers.
I have this line in make.conf
OPTIONS_UNSET= X11 GUI CUPS DOCS EXAMPLES NLS
Now I need www/x
** The following ports have an incorrect PKGORIGIN **
PKGORIGIN connects packaged or installed ports to the directory they
originated from. This is essential for tools like pkg_version or
portupgrade to work correctly. Wrong PKGORIGINs are often caused by a
wrong order of CATEGORIES after a re
Hi,
Only 9 days left until the proposed deadline to add staging support to all
ports. My question is: what will happen that day with unstaged ports that have
submitted staging patches? It seems that there are at least 140 such ports:
https://bugs.freebsd.org/bugzilla/buglist.cgi?list_id=6879&qu
Hi!
> Only 9 days left until the proposed deadline to add staging support
> to all ports. My question is: what will happen that day with unstaged
> ports that have submitted staging patches?
>From what I understand: Not much for additional 2 month.
The plan was to remove the unstaged, deprecated
The latest version of "libgcrypt" available in the ports system is
libgcrypt-1.5.3_2; however, the latest stable version is Libgcrypt 1.6.1,
released on 29 January 2014, (http://directory.fsf.org/wiki/Libgcrypt).
Are there any plans to update this port?
--
Jerry
_
21.06.2014, 15:37, "Kurt Jaeger" :
> Hi!
>> Only 9 days left until the proposed deadline to add staging support
>> to all ports. My question is: what will happen that day with unstaged
>> ports that have submitted staging patches?
>
> From what I understand: Not much for additional 2 month.
>
>
Please checkout the newest bmon v3.2 version at https://github.com/tgraf/bmon
Source code had been updated to support freebsd/osx
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any
Cy, thanks for your recent updates. tripwire builds nicely with clang
now, but poudriere is running into a staging error:
>> Failed ports: security/tripwire:stage
poudriere build log attached.
Now that the port is no longer interactive, is the intent to package the
install.sh script so t
On Sat, 2014-06-21 at 11:28 -0500, Greg Rivers wrote:
> Cy, thanks for your recent updates. tripwire builds nicely with clang
> now, but poudriere is running into a staging error:
>
> >> Failed ports: security/tripwire:stage
>
> poudriere build log attached.
>
> Now that the port is no lon
Hello;
Some java ports, especially from ASF projects, commonly use maven
to build and maven is meant to be a ports-like system to fetch
dependencies as part of the build. Maven has it's own repository:
http://search.maven.org/#browse
This is a problem with the Apache POI port but it is also an i
On Sat, Jun 21, 2014 at 12:02:32PM -0500, Pedro Giffuni wrote:
> This is a problem with the Apache POI port but it is also an issue
> with a potential Apache hadoop update: apparently our cluster
> doesn't like ports that download stuff as part of their build
s/doesn't like/doesn't allow/
This is
In message , Greg
Rivers
writes:
> Cy, thanks for your recent updates. tripwire builds nicely with clang
> now, but poudriere is running into a staging error:
>
> >> Failed ports: security/tripwire:stage
>
> poudriere build log attached.
>
> Now that the port is no longer interactive, is
On 21 June 2014 06:45, Ivan Rokotov wrote:
> 21.06.2014, 15:37, "Kurt Jaeger" :
>> Hi!
>>> Only 9 days left until the proposed deadline to add staging support
>>> to all ports. My question is: what will happen that day with unstaged
>>> ports that have submitted staging patches?
>>
>> From what
Zilvinas Valinskas wrote:
> Please checkout the newest bmon v3.2 version at
> https://github.com/tgraf/bmon
> Source code had been updated to support freebsd/osx
> ___
> freebsd-ports@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo
In message , Greg
Rivers
writes:
> This message is in MIME format. The first part should be readable text,
> while the remaining parts are likely unreadable without MIME-aware tools.
>
> --487545500-2130553633-1403368130=:10559
> Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
>
Cy Schubert writes:
> In message , Greg
> Rivers
> writes:
> > This message is in MIME format. The first part should be readable text,
> > while the remaining parts are likely unreadable without MIME-aware tools.
> >
> > --487545500-2130553633-1403368130=:10559
> > Content-Type: TEXT/PLAIN;
Hi,
Is there any major difference in between devel/subversion and stock svnlite
in 10.X system? If so what are those?
Thanks in advance.
BR,
Muhammad
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
On Fri, 20 Jun 2014, Paul Schmehl wrote:
I am the maintainer for security/sguil-server, security/sguil-sensor and
security/sguil-client. I am officially abandoning the ports. The
security/sguil-server port is not staged. The other two are. The software
has a new release out, so all three po
Marco Steinbach wrote:
Marco Steinbach wrote on 20.06.2014 02:06:
Marco Steinbach wrote on 19.06.2014 23:49:
Miroslav Lachman schrieb:
I don't need DOCS, EXAMPLES etc. for each port as I normaly do not
use them on servers.
I have this line in make.conf
OPTIONS_UNSET= X11 GUI CUPS DOCS EXAMPLE
Hi,
I submitted a patch[1] to update from 1.5.3 to 1.6.1
Regards,
--
Carlos Jacobo Puga Medina
[1] https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=191256
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-p
21.06.2014, 19:19, "Eitan Adler" :
>> I gather that they will be marked as 'DEPRECATED' and set as
>> non-maintained.
>> DEPRECATED ports can't be installed, AFAIK.
>
> They can be.
Mea culpa, sorry. I've just checked, they can indeed.
>> I'm not a maintainer myself, but I guess that people w
On Sat, Jun 21, 2014 at 03:45:53PM +0200, Ivan Rokotov wrote:
> 21.06.2014, 15:37, "Kurt Jaeger" :
> > Hi!
> >> Only 9 days left until the proposed deadline to add staging support
> >> to all ports. My question is: what will happen that day with unstaged
> >> ports that have submitted staging pa
On Sat, 21 Jun 2014 23:02:07 +0200, Carlos Jacobo Puga Medina stated:
> I submitted a patch[1] to update from 1.5.3 to 1.6.1
Thanks!
--
Jerry
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubsc
29 matches
Mail list logo
