The 2014Q4 ports tree has been doing very well with getting security
updates in a more timely fashion.
It seemed worthwhile to point out that that hard (and tedious) work is
being noticed and (much!) appreciated.
Thanks!
___
freebsd-ports@freebsd.org ma
Hello,
When the quarterly ports trees were introduced, they were described as
including security, build, and runtime fixes for 3 months.
This is a great idea, and with 2014Q2 it seemed to work pretty well.
However, it doesn't seem like 2014Q3 is getting security fixes.
For example, the openssl p
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
Whenever I build a ports list with Haskell modules in it, poudriere
insists on rebuilding those Haskell modules every time, claiming the
options have changed. The options haven't changed; it will happily
report this even if run twice in a row on a system with no other
activity in between:
>>
On Thu, Apr 3, 2014 at 11:36 AM, Mathieu Arnold wrote:
> Something built for perl 5.14.0 will work with perl 5.14.5.a6_7.
This is one of those things that's true most of the time. And on
those occasions when it isn't, the fallout is spectacular. It does
not come up more often because poudriere
On Wed, Apr 2, 2014 at 6:41 AM, Mathieu Arnold wrote:
> +--On 1 avril 2014 11:18:05 -0400 J David wrote:
> | from perl-5.12.3.4_5a to 5.12.3.4_5a1.
>
> Perl 5.12 has been removed about a month and half ago, so, if you were
> still using it, it's going to be a pain, you sh
On Tue, Apr 1, 2014 at 11:38 AM, Matthew Seaman wrote:
> This is why the quarterly branches exist. 2014Q1 (Just EoL'd) and
> 2014Q2 (just branched from head) will now get only security and port-fix
> type upgrades for the next 3 months. Therefore if your poudriere repo
> had been tracking 2014Q1
Poudriere and pkgng have been great tools for managing large numbers
of FreeBSD ports.
However, we would like to optimize the build in some cases.
Consider a poudriere-generated pkgng repository with about 10,000
packages in it. Now, just because the FreeBSD ports collection is the
way it is, ab
On Sun, Mar 16, 2014 at 3:45 PM, olli hauer wrote:
> run the following command and pkgng will take care of the renamed port.
> #> pkg set -o mail/p5-Mail-SpamAssassin:mail/spamassassin
That works perfectly. Thanks very much!
___
freebsd-ports@freebsd.o
Is there a best practice for what to do with pkgng when ports
maintainers randomly rename ports? (E.g. mail/p5-Mail-SpamAssassin
being moved to mail/spamassassin a few days ago without notice or
warning or documentation in UPDATING.)
Prior to pkgng, we used to use pkg_replace for this. portmaster
Hello,
When attempting to build the port lang/racket under poudriere, the
following message is generated:
>> Ignoring lang/racket: has to be built manually: i386 requires
kern.maxdsiz="640M" to build
This is on a machine with kern.maxdsiz=32G.
What is the best way to build this package so t
On Wed, Apr 3, 2013 at 11:23 AM, Volodymyr Kostyrko wrote:
> That's a known problem, the file was migrated from gettext to libiconv.
>
> See UPDATING@20130316
Thank you very much, problem solved. :)
___
freebsd-ports@freebsd.org mailing list
http://lis
We recently freed up a couple of machines to start moving toward helping
test and using pkgng.
For testing purposes, we have two parallel build machines running
9.1-STABLE, one running poudriere, and one running portmaster.
While building converters/libiconv with portmaster we hit the following:
On Fri, Mar 22, 2013 at 2:11 PM, John Marino wrote:
> I wouldn't be so quick to blame poudriere.
>
I'm not interested in "blaming" anyone... it is probably a config problem.
I simply asked how to get the error output for a port built inside
poudriere. And this:
> e.g. look in /usr/local/poud
We are rapidly converting all of our ports-building infrastructure to
poudriere, which is a fantastic tool and has been a huge improvement for us.
However, I do run across the occasional stubborn ports that refuse to build
(example: lang/ghc) under poudriere, and I'm not sure how to debug this.
I
15 matches
Mail list logo
