On Tue, 5 Dec 2017 08:35:55 +0100
Stefan Esser wrote:
> Am 05.12.17 um 00:43 schrieb Tatsuki Makino:
> > By the way, where is the clever way to update to flavor?
> > I am using portmaster.
>
> I'm working on FLAVOR support in portmaster. My version did already
> build all
Le 04/12/2017 à 18:33, Steve Kargl a écrit :
> On Mon, Dec 04, 2017 at 11:49:30AM +, Alan Hicks wrote:
>>
>> On 02/12/2017 17:28, Steve Kargl wrote:
>>> On Sat, Dec 02, 2017 at 02:06:32PM +0100, Christian Ullrich wrote:
* Steve Kargl wrote:
>>> Given that I asked about a specific
Hi all,
I thought quarterly ports branches would receive security fixes from
HEAD but no other version bumps.
If this is correct, then why is MySQL 5.6 in Q4 one version behind HEAD
(updated 6 weeks ago) and with all the critical security issues still present?
On 05/12/2017 04:51, Michelle Sullivan wrote:
Steven Hartland wrote:
On Mon, 4 Dec 2017 at 03:02, Michelle Sullivan
wrote:
You mean if you're not into security or part of a security company stay
on quarterly, but if you need to keep patched up because you are in the
top
On 05/12/2017 08:13, Mathieu Arnold wrote:
Le 04/12/2017 à 18:33, Steve Kargl a écrit :
On Mon, Dec 04, 2017 at 11:49:30AM +, Alan Hicks wrote:
On 02/12/2017 17:28, Steve Kargl wrote:
On Sat, Dec 02, 2017 at 02:06:32PM +0100, Christian Ullrich wrote:
* Steve Kargl wrote:
Given that I
First some background (my typical use cases for ports):
0. FreeBSD lilith 11.1-RELEASE FreeBSD 11.1-RELEASE #0 r321664: Fri Jul 28
23:35:18 EDT 2017 root@lilith:/usr/obj/usr/src/sys/GENERIC amd64
1. Daily routine (current):
cd /usr/src
svn update (from 11.1-RELEASE)
[make
> On 05.12.2017 08:35, Stefan Esser wrote:
> > Am 05.12.17 um 00:43 schrieb Tatsuki Makino:
> > > By the way, where is the clever way to update to flavor?
> > > I am using portmaster.
> > I'm working on FLAVOR support in portmaster. My version did already build
> > all updated ports, the FLAVOR
On Tue, Dec 05, 2017 at 08:35:55AM +0100, Stefan Esser wrote:
> ...
> I'm working on FLAVOR support in portmaster. My version did already build
> all updated ports, the FLAVOR parameter is passed to build sub-processes,
> but there is still some confusion between multiple flavored versions of the
> Am 05.12.2017 um 12:05 schrieb Patrick M. Hausen :
> PHP 5.6 is 5.6.31 in Q4 with CVE-2016-1283 and 5.6.32 in HEAD.
> Update to HEAD 4 weeks ago.
>
> Curl is behind, too - though this fix was committed to HEAD just 2 days ago.
And graphics/OpenEXR received security updates in
Aloha Stefan,
On 05.12.2017 08:35, Stefan Esser wrote:
Am 05.12.17 um 00:43 schrieb Tatsuki Makino:
By the way, where is the clever way to update to flavor?
I am using portmaster.
I'm working on FLAVOR support in portmaster. My version did already build
all updated ports, the FLAVOR parameter
Hi!
> I thought quarterly ports branches would receive security fixes from
> HEAD but no other version bumps.
>
> If this is correct, then why is MySQL 5.6 in Q4 one version behind HEAD
> (updated 6 weeks ago) and with all the critical security issues still present?
Maintainer just committed
Hi all,
> Am 05.12.2017 um 11:55 schrieb Kurt Jaeger :
>
> Hi!
>
>> I thought quarterly ports branches would receive security fixes from
>> HEAD but no other version bumps.
>>
>> If this is correct, then why is MySQL 5.6 in Q4 one version behind HEAD
>> (updated 6 weeks ago)
On 12/5/2017 1:53 AM, Aryeh Friedman wrote:
> 1. I decide to try poudriere since it seems to what people are raving
> about. What a 'ing confusing mess it is use After deciding it
> is over kill I go to option 2
1 time setup:
echo ZPOOL=zroot >> /usr/local/etc/poudriere.conf
poudriere
On 12/1/2017 9:59 AM, Kevin Oberman wrote:
> First, welcome flavors. It has been badly needed for a while and is going
> to clean up a couple of messes that have been plaguing the port system for
> a long time.
I plan to look at portupgrade + FLAVORS support in the next few weeks as
well.
--
The cmake test just tries to compile:
#include
std::atomic x;
int main() {
return x;
}
What happens if you try to compile this small code with your host compiler?
Roman
On Tue, Dec 05, 2017 at 10:42:49AM -0800, Mark Millard wrote:
> [I experiment with system-clang based
> buildworld and/or
Le 03/12/2017 à 03:30, Adam Weinberger a écrit :
>> On 2 Dec, 2017, at 18:57, Yuri wrote:
>>
>> Build opens too many file descriptors, and fails:
>>
>> http://beefy5.nyi.freebsd.org/data/103i386-default/455387/logs/RStudio-1.1.385.log
>>
>>
On 12/05/17 17:09, Mathieu Arnold wrote:
Le 05/12/2017 à 10:53, Aryeh Friedman a écrit :
TL;DR;
Flavors 'ed up ports and there are no good ways/alternates for how
to use the ports collection for normal everyday users/maintainers
Thank you for supporting all the hard work and countless
On 12/4/2017 11:35 PM, Stefan Esser wrote:
> Is it acceptable, to have portmaster stop supporting the old package system?
> AFAIK, there is no way that a modern ports tree with flavor support works
> with a non-PKG_NG infrastructure?
100% yes.
If someone needs pkg_* support for an older tree then
On 12/05/17 04:53, Aryeh Friedman wrote:
First some background (my typical use cases for ports):
0. FreeBSD lilith 11.1-RELEASE FreeBSD 11.1-RELEASE #0 r321664: Fri Jul 28
23:35:18 EDT 2017 root@lilith:/usr/obj/usr/src/sys/GENERIC amd64
1. Daily routine (current):
cd /usr/src
On Tue, Dec 05, 2017 at 08:42:27AM -0800, Chris H wrote:
> IMHO it might be a good idea to make a legacy branch, in the ports
> tree before gutting the pre-NG stuff.
Good lord, people.
The pre-NG stuff has Left The Building. It is not coming back.
The last (even trivial) revision to the pkg_*
Le 05/12/2017 à 10:53, Aryeh Friedman a écrit :
> TL;DR;
> Flavors 'ed up ports and there are no good ways/alternates for how
> to use the ports collection for normal everyday users/maintainers
Thank you for supporting all the hard work and countless hours that so
many volunteers put in making
[I experiment with system-clang based
buildworld and/or buildkernel based
TARGET_ARCH=powerpc64 and
TARGET_ARCH=powerpc environments.]
For TARGET_ARCH=powerpc devel/llvm40 and
devel/llvm50 get failure reports like:
-- Looking for __atomic_load_8 in atomic - not found
CMake Error at
I have the project that uses xdg-utils to install the desktop-related
files. It installs them under $XDG_DATA_HOME into ${WRKDIR}.
Is this a mistake? Shouldn't it be ${STAGEDIR}${PREFIX}/share?
Yuri
___
freebsd-ports@freebsd.org mailing list
[I experiment with system-clang based
buildworld and/or buildkernel based
TARGET_ARCH=powerpc64 and
TARGET_ARCH=powerpc environments.]
linking miniruby
generating encdb.h
/wrkdirs/usr/ports/lang/ruby23/work/ruby-2.3.5/tool/vpath.rb:18: [BUG]
Segmentation fault at 0x256400cf
ruby 2.3.5p376
Am 05.12.2017 um 08:35 schrieb Stefan Esser:
> Am 05.12.17 um 00:43 schrieb Tatsuki Makino:
>> By the way, where is the clever way to update to flavor?
>> I am using portmaster.
>
> I'm working on FLAVOR support in portmaster. My version did already build
> all updated ports, the FLAVOR parameter
On Tue, Dec 05, 2017 at 09:13:38AM +0100, Mathieu Arnold wrote:
> Le 04/12/2017 à 18:33, Steve Kargl a écrit :
> > On Mon, Dec 04, 2017 at 11:49:30AM +, Alan Hicks wrote:
> >>
> >> On 02/12/2017 17:28, Steve Kargl wrote:
> >>> On Sat, Dec 02, 2017 at 02:06:32PM +0100, Christian Ullrich wrote:
Hi,
On Tue, Dec 05, 2017 at 08:35:55AM +0100, Stefan Esser wrote:
> Is it acceptable, to have portmaster stop supporting the old package system?
> AFAIK, there is no way that a modern ports tree with flavor support works
> with a non-PKG_NG infrastructure?
I also started working on this
On Mon, 2017-12-04 at 18:10 +0100, Jan Beich wrote:
> Dennis Glatting writes:
>
> > 1) I am tired of port breakage. I am past tired of being told to
> > read
> > UPDATEs when UPDATEs often has limited information, including
> > install
> > conflicts.
> >
> > 2) "Error 70"
On Tue, 5 Dec 2017 08:35:55 +0100
Stefan Esser wrote:
> Am 05.12.17 um 00:43 schrieb Tatsuki Makino:
> > By the way, where is the clever way to update to flavor?
> > I am using portmaster.
>
> I'm working on FLAVOR support in portmaster. My version did already build
> all
On 5 December 2017 at 22:53, Aryeh Friedman wrote:
[...]
> 2. I installed synth (2.00) and *ATTEMPTED* to do a upgrade-system with the
> following results (still not a successful run):
>
> a. Hard freezes the machine (not even a kernel panic) 4 times in a row
synth
Hi all,
On Mon, Dec 04, 2017 at 10:31:47PM +0100, Jan Beich wrote:
> Koen Martens writes:
>
> > I've installed poudriere through pkg, which gives me 3.1.22 at the
> > moment. I'll try 3.2 from ports tomorrow, wasn't aware that the binary
> > packages had an out of date
On Tue, 5 Dec 2017 03:33:10 -0800 "David Wolfskill" said
On Tue, Dec 05, 2017 at 08:35:55AM +0100, Stefan Esser wrote:
> ...
> I'm working on FLAVOR support in portmaster. My version did already build
> all updated ports, the FLAVOR parameter is passed to build
On 12/02/17 18:30, Adam Weinberger wrote:
Then MAKE_JOBS_NUMBER_LIMIT (or MAKE_JOBS_UNSAFE) would be my next step. If it
fails on the beefy builders, it's likely to fail on resource-starved end-user
boxes. The builders do many concurrent builds, but it's possible for end-users
to hit that
On Tue, Dec 05, 2017 at 05:25:13PM -0500, Baho Utot wrote:
> Thank you for taking a perfectly good system and breaking it as well as
> making it unusable, unstable.
You made your point 10 posts ago.
You are repeating yourself.
Why???
mcl
___
On 2017-Dec-5, at 12:39 PM, Roman Divacky wrote:
> The cmake test just tries to compile:
>
> #include
> std::atomic x;
> int main() {
> return x;
> }
>
> What happens if you try to compile this small code with your host compiler?
>
> Roman
[I later show that it seems to be testing
with:
> On 5 Dec, 2017, at 15:00, Mathieu Arnold wrote:
>
> Le 03/12/2017 à 03:30, Adam Weinberger a écrit :
>>> On 2 Dec, 2017, at 18:57, Yuri wrote:
>>>
>>> Build opens too many file descriptors, and fails:
>>>
>>>
Stefan Esser writes:
Hi Stefan
> Is it acceptable, to have portmaster stop supporting the old package system?
I think so.
Thanks for your work on this.
Éric Masson
--
Discuter tranquillement avec Michel Guillou???
Je n'ai JAMAIS vu quelqu'un de plus *facho* que ce type.
On 12/05/17 23:25, Baho Utot wrote:
> Thank you for taking a perfectly good system and breaking it as well as
> making it unusable, unstable. You just don't know of all the countless
> hours spent after running an update and taking a week to get it working
> again.
>
> It really helps motivate
On Tue, 5 Dec 2017 13:48:12 -0600 "Mark Linimon" said
On Tue, Dec 05, 2017 at 08:42:27AM -0800, Chris H wrote:
> IMHO it might be a good idea to make a legacy branch, in the ports
> tree before gutting the pre-NG stuff.
Good lord, people.
The pre-NG stuff has Left The
I wonder if making a simple man page for general users would be wise and
referencing the fully featured man page in it for more experienced users?
It seems that many users want a simple route and the current man page is
simply too intimidating for them to even consider attempting to use. A
small
FreeBSD 10.3-RELEASE-p24
FreeBSD clang version 3.4.1 (from base)
GNU gdb 6.1.1 (from base)
I'm trying to debug a crash in the multimedia/tvheadend 4.2.3 server on
the above system when playing a recorded program on tvheadend's Android
client. It reliably crashes when I try to fast forward. But
[I experiment with clang-based worlds and kernels
on powerpc64 and powerpc. But I'm not sure that
such is the only type of context is required to
see the below problem.]
Attempting to build lang/gcc7 on a system-clang based
powerpc64 (world and kernel) gets:
On 2017-12-05 12:32, Patrick M. Hausen wrote:
We relied on just updating the branch every night and running
poudriere ... looks
like I should implement something around pkg audit that sends us daily
status
reports.
Yes, but note that pkgaudit depends on VuXML which is also not up to
date
On Tue, Dec 05, 2017 at 04:53:07AM -0500, Aryeh Friedman wrote:
> First some background (my typical use cases for ports):
>
> 0. FreeBSD lilith 11.1-RELEASE FreeBSD 11.1-RELEASE #0 r321664: Fri Jul 28
> 23:35:18 EDT 2017 root@lilith:/usr/obj/usr/src/sys/GENERIC amd64
>
> 1. Daily routine
On 12/05/17 02:35, Stefan Esser wrote:
> [...]
> Is it acceptable, to have portmaster stop supporting the old package system?
> AFAIK, there is no way that a modern ports tree with flavor support works
> with a non-PKG_NG infrastructure?
>
> Regards, STefan
> [...]
One vote here for dropping old
On 12/05/17 03:13, Mathieu Arnold wrote:
> Le 04/12/2017 à 18:33, Steve Kargl a écrit :
>> [...]
>> This does not document the change in ports/UPDATING. FreeBSD
>> users have been told to check {src/ports}/UPDATING for 20+
>> years. A change that fundamentally changes the way users
>> interact
> On 5 Dec, 2017, at 0:35, Stefan Esser wrote:
>
> Am 05.12.17 um 00:43 schrieb Tatsuki Makino:
>> By the way, where is the clever way to update to flavor?
>> I am using portmaster.
>
> I'm working on FLAVOR support in portmaster. My version did already build
> all updated
47 matches
Mail list logo