- Stage support
PR: 190633
-
Build ID: 20140605014000-37110
Job owner: m...@freebsd.org
Buildtime: 2 days
Enddate: Sat, 07 Jun 2014 08:26:27 GMT
Revision: 356566
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 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
On 07/06/2014 04:34, Jim Trigg wrote:
> I'm looking to port a utility from Ubuntu, and need to know what hooks
> there are in pkg. I want to port etckeeper, a tool that automates
> version control for /etc (and in our case $PREFIX/etc). Its current
> implementation uses hooks in apt to automaticall
Baptiste Daroussin wrote:
> The mental genius is me apparently (thanks for the kind words, btw) I'm
> responsible for both the pkg_install EOL message and for breaking ports tree
> with older make (btw you can recover with installing manually bmake).
>
That is quite a task... you can't easily
Jerry wrote:
> Really ...
> Hi, I am a FreeBSD user, and I would like to report a problem that doesn't
> exist. I have a theoretical solution for this unknown problem, but I cannot
> test it because I cannot create the environment.
>
> Seriously, there are plenty of real problems. Attempting to ant
Paul Schmehl wrote:
>
> I appreciate the advice. I've elected to setup an alternate form of
> backup (using rsync over ssh to backup each server to its sibling) so
> I can upgrade to 8.4 without worrying about a loss. Once that's
> complete, I'll get the new backup system in place (using Storgrid
Seems every week or two my build servers all fail and it's mostly one of
2 packages
devel/gobject-introspection
dns/bind99
Today its gobject-introspection:
checking for backtrace_symbols... no
checking whether /usr/local/bin/python2.7 version is >= 2.5... yes
checking for /usr/local/bin/python2.
On behalf of the FreeBSD python team, I'd like to announce the availability of
concurrent, conflict-free python package support in the ports tree.
Why?
FreeBSD supports different python versions and flavours to be installed at
the same time, such as e.g. Python 2.7 and Python 3.3. Ports insta
Marcus von Appen wrote:
> On behalf of the FreeBSD python team, I'd like to announce the availability of
> concurrent, conflict-free python package support in the ports tree.
>
> Why?
>
> FreeBSD supports different python versions and flavours to be installed at
> the same time, such as e.g. Py
--On June 7, 2014 at 1:32:08 PM +0200 Michelle Sullivan
wrote:
Paul Schmehl wrote:
I appreciate the advice. I've elected to setup an alternate form of
backup (using rsync over ssh to backup each server to its sibling) so
I can upgrade to 8.4 without worrying about a loss. Once that's
compl
Michelle Sullivan wrote:
> Seems every week or two my build servers all fail and it's mostly one of
> 2 packages
>
> devel/gobject-introspection
> dns/bind99
>
> Today its gobject-introspection:
>
Actually it's both... :/
install -o root -g wheel -m 444
/wrkdirs/usr/ports/dns/bind99/work/bind
Hello, Vick.
You wrote 22 мая 2014 г., 22:18:10:
VK> I was wondering if you would be open to peeling off the mod_dav_svn
VK> from being an option in the subversion port to being its own port that
VK> depends on this one, or making a sub-port that installs subversion
VK> with it enabled under a dif
I'm an oldtimer, having used the port building system for years. Recently
I upgraded two servers to 8.4 and implemented the pkgng system. Now, when
I run portmaster -ad, it seems to keep reinstalling the same ports over and
over again.
Is portmaster not the appropriate method for updating po
On 06/06/2014 21:38, Christian Weisgerber wrote:
On 2014-06-04, Chris Whitehouse wrote:
I have experienced firefox and/or xorg apparently freezing for several
seconds which seems to be due to loading a page with a large image.
That's a well-known problem. It can be worked around by setting
- Add sysutils/grub2-pcbsd
This installs PC-BSD's custom grub 2.02-prerelease, which includes
various enhancements for Boot-Environments and ZFS support
-
Build ID: 20140606152801-40285
Job owner: kmo...@free
Hi,
On Sat, Jun 7, 2014 at 9:03 PM, Paul Schmehl wrote:
> I'm an oldtimer, having used the port building system for years. Recently I
> upgraded two servers to 8.4 and implemented the pkgng system. Now, when I
> run portmaster -ad, it seems to keep reinstalling the same ports over and
> over ag
Hello, Ports.
I've learned proper way to split subversion into several ports. Question
is: how fine-grained should I do this? I want to split it at least into:
(1) devel/subversion-libs-- base libs, used by all other ports. Options
about SERF, BDB and SASL go
--On June 7, 2014 at 10:04:17 PM +0200 Torfinn Ingolfsen
wrote:
Hi,
On Sat, Jun 7, 2014 at 9:03 PM, Paul Schmehl
wrote:
I'm an oldtimer, having used the port building system for years.
Recently I upgraded two servers to 8.4 and implemented the pkgng system.
Now, when I run portmaster -ad, i
Paul Schmehl wrote:
> Recently I upgraded two servers to 8.4 and implemented the pkgng system.
[snip]
> Is portmaster not the appropriate method for updating ports with pkgng?
It depends whether you're talking about *building* packages from the ports
tree or installing binary packages.
As for bu
On Fri 2014-06-06 17:17:40 UTC+0200, Baptiste Daroussin (b...@freebsd.org)
wrote:
> Yes it would have been a good idea to give a warning to the user about
> the fact that the ports tree won't be support long on after EOL of
> 8.3, given the ports tree will break again quite soon after EOL of 8.4
--On June 7, 2014 at 10:22:41 PM +0200 "A.J. 'Fonz' van Werven"
wrote:
Paul Schmehl wrote:
Recently I upgraded two servers to 8.4 and implemented the pkgng system.
[snip]
Is portmaster not the appropriate method for updating ports with pkgng?
It depends whether you're talking about *buil
On 2014-06-07 22:40, Paul Schmehl wrote:
> --On June 7, 2014 at 10:22:41 PM +0200 "A.J. 'Fonz' van Werven"
> wrote:
>
>> Paul Schmehl wrote:
>>
>>> Recently I upgraded two servers to 8.4 and implemented the pkgng system.
>> [snip]
>>> Is portmaster not the appropriate method for updating ports w
On 2014-06-07 19:10, Lev Serebryakov wrote:
> Hello, Vick.
> You wrote 22 мая 2014 г., 22:18:10:
>
> VK> I was wondering if you would be open to peeling off the mod_dav_svn
> VK> from being an option in the subversion port to being its own port that
> VK> depends on this one, or making a sub-port
I'm looking at changing the devel/quilt port to support stageing. I've read the
manual and know that there will be a variable STAGEDIR defined somewhere. But
where exactly? It seems it is defined in the environment of the FreeBSD ports
Makefile, but it is not available as a unix shell environmen
On 2014-06-07 22:41, Dirk Jagdmann wrote:
> I'm looking at changing the devel/quilt port to support stageing. I've read
> the manual and know that there will be a variable STAGEDIR defined somewhere.
> But where exactly? It seems it is defined in the environment of the FreeBSD
> ports Makefile,
> On 07 Jun 2014, at 23:16, olli hauer wrote:
>
>> On 2014-06-07 22:40, Paul Schmehl wrote:
>> --On June 7, 2014 at 10:22:41 PM +0200 "A.J. 'Fonz' van Werven"
>> wrote:
>>
>>> Paul Schmehl wrote:
>>>
Recently I upgraded two servers to 8.4 and implemented the pkgng system.
>>> [snip]
>>
On 6/7/2014 18:52, Paul Schmehl wrote:
> I've searched. There's no notice in UPDATING. There was no
> announcement on the ports list. I found NOTHING to warn me of this
> problem except other people complaining of the same problem. 8.4 went
> EOL in September 2012. This problem was introduced w
On Sun, Jun 08, 2014 at 12:42:27AM +0200, John Marino wrote:
> The next time you are right will be the first time. [...] You are being
> ridiculed because you're a boor and consistently wrong, which is not a
> good combination.
None of the above represents what I think FreeBSD ought to be about.
For the record bmake doesn't work is fails to build qmake4 without even
giving an error :(
Where as copying make from 10 to the 8.3 box worked fine.
Regards
steve
- Original Message -
From:
To:
Sent: Sunday, May 11, 2014 12:11 AM
Subject: Re: Unable to use ports on 8.3 or earli
HAY I hope you check your mail soon and call me Bryan 949-566-4872 I am in
Newport by airport
Sincerely & Respectfully:
BRYAN E CURELL.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, sen
I was updating make.conf on a build machine today and noticed that
OPTIONS_UNSET=X11 was not working. Digging around, I found that if
OPTIONS_UNSET=X11 was set before OPTIONS_UNSET=JAVA, OPTIONS_UNSET=X11 didn't
happen. WITHOUT_X11=YES worked in all cases. Is this expected behavior or a
bug?
I take it back this fails for qt4-rcc which fails to detect endian
and other issues :(
So far Lena's suggestion of an 8.4 make is working :)
- Original Message -
From: "Steven Hartland"
For the record bmake doesn't work is fails to build qmake4 without even
giving an error :(
Where
Its a single option so you need:
OPTIONS_UNSET=X11 JAVA
- Original Message -
From: "Dave Duchscher"
To:
Sent: Sunday, June 08, 2014 3:36 AM
Subject: Global options ordering bug?
I was updating make.conf on a build machine today and noticed that OPTIONS_UNSET=X11 was not working. Di
Thanks. I new this but for some reason I just couldn't see it. I had used +=
in other paces but for some reason was not doing it here. *sigh*
--
DaveD
On Jun 7, 2014, at 9:39 PM, Steven Hartland wrote:
> Its a single option so you need:
> OPTIONS_UNSET=X11 JAVA
>
> - Original Message -
Call me 949-566-4872 I am in Newport inch by J. W. I need some love, I am
very Lonely GOING through break up.
Sincerely & Respectfully:
BRYAN E CURELL.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
On Sat, Jun 7, 2014 at 5:24 PM, Mark Linimon wrote:
> On Sun, Jun 08, 2014 at 12:42:27AM +0200, John Marino wrote:
> > The next time you are right will be the first time. [...] You are being
> > ridiculed because you're a boor and consistently wrong, which is not a
> > good combination.
>
> None
40 matches
Mail list logo
