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
W dniu 2014-05-21 03:53, Robert Backhaus pisze:
> The fact that those two ports install conflicting binaries isn't a problem.
> The problem is that you were allowed to install the second port.
>
> With mplayer, there is a correct CONFLICTS line in mplayer2, but does not
> appear to be one in mpla
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
[jakobbg@core2 /usr/ports/mail/postfix-current]$ sudo make distclean &&
sudo make
===> Cleaning for postfix-base-2.12.20140507,4
===> Deleting distfiles for postfix-base-2.12.20140507,4
===> License IPL10 accepted by the user
===> Found saved configuration for postfix-base-2.12.20140507,4
===>
On 20/05/2014 22:13, Tijl Coosemans wrote:
> On Tue, 20 May 2014 08:52:46 -0700 Kevin Oberman wrote:
>> Removed the FIND and re-built. After the build I looked in
>> stage/usr/local/lib and the .so.0 files are still present! I then installed
>> with no errors. I'll admit that I don't understand wha
Ronald F. Guilmette wrote:
Please allow me to clarify two things:
1) The exact set of build options that are needed in order to reproduce
the crash I have reported are as follows:
DBUS (enabled by default)
GIO (enabled by default)
GSTREAMER (enabled by default)
On Wed, 21 May 2014 11:26:57 +0200 Dominic Fandrey wrote:
> On 20/05/2014 22:13, Tijl Coosemans wrote:
>> On Tue, 20 May 2014 08:52:46 -0700 Kevin Oberman wrote:
>>> Removed the FIND and re-built. After the build I looked in
>>> stage/usr/local/lib and the .so.0 files are still present! I then inst
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
Hello,
databases/qdbm port fails to build on 9.2 amd64, see attached log.
I would guess it ignores CFLAGS.
Best regards
Andreas
qdbm-1.8.78_1.log
Description: Binary data
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis
Hi,
the programs star and smake seem to have disappeared from the FreeBSD ports
collection.
The supposed reason is: "no longer compiles"
but it seems that the real reason is that somebody did modify the build system
in a way that harms portability and this way caused a FreeBSD change
(intro
Update distinfo since the DESCRIPTION file was updated when the module
was marked as orphaned
-
Build ID: 20140521124600-3594
Job owner: skreu...@freebsd.org
Buildtime: 16 minutes
Enddate:
On Wed, May 21, 2014 at 2:07 AM, Matthew Seaman
wrote:
> Try
>
> CHECK_CHANGED_OPTIONS=verbose
>
> in /usr/local/etc/poudriere.conf ?
Great suggestion, thanks!
With just one Haskell port, hs-text, here's what happens:
>> Calculating ports order and dependencies
>> Sanity checking the r
Dear Joerg,
The only problem is that if such port is unmaintained (its maintainer email
address is po...@freebsd.org) there's no one who could do such thing,
because commiters are busy working on the entire ports tree, and apparently
no one from maintainers was interested in the port to do so. If
All of my freebsd boxes are headless, and I build all ports without
X11. To accomplish this, I specify in make.conf the following:
WITHOUT_GNOME=yes
WITHOUT_X11=yes
OPTIONS_UNSET=X11 GUI
I have to specify both WITHOUT_X11 and OPTIONS_UNSET since I have
found some ports to not honor OPTIONS_UNSET
Good afternoon
I wanted to get in touch and let you know we just launched LandR which is the
worlds first intelligent online mastering service. It's a spectral analysis
system that listens to music and detects detailed features in the audio signals
to give a studio-quality master. Here's a lin
On 05/20/14 22:10, Matthias Andree wrote:
Am 21.05.2014 03:49, schrieb Paul Schmehl:
Thanks. With some of my ports I have been really struggling trying to
get staging working. I'd be very interested to see what you did, since
it was apparently easy for you to do.
A bit of experience with pac
On Wed, 21 May 2014 14:58:32 -0700
Patrick Powell wrote:
> Mathias, I think that brief description of how you did this would be
> VERY useful to some of us looking at this problem and not knowing
> where to start. Perhaps an: 'this is the way it was' and a 'this is
> the way it should be' doc
2014-05-21 17:24 GMT+02:00 J David :
> Probably there is some
> widget in the lang/ghc package that's needed to build the
> documentation.
Yes, there is. That is called Haddock, the documentation tool similar
to Javadoc and Doxygen. Since it parses the same source code as the
compiler itself, an
Bob Eager wrote:
> On Wed, 21 May 2014 14:58:32 -0700
> Patrick Powell wrote:
>
>
>> Mathias, I think that brief description of how you did this would be
>> VERY useful to some of us looking at this problem and not knowing
>> where to start. Perhaps an: 'this is the way it was' and a 'this
Am 21.05.2014 23:58, schrieb Patrick Powell:
> Mathias, I think that brief description of how you did this would be
> VERY useful to some of us looking at this problem and not knowing where
> to start. Perhaps an: 'this is the way it was' and a 'this is the way
> it should be' document would be
23 matches
Mail list logo
