On 2020-12-27 15:49, Dan Mahoney (Gushi) wrote:
Ergo, I am wondering what the best way forward is to get a reasonably
patched version of openssl that has old ciphers turned on (since it is
still possible at compile-time, the code hasn't been outright removed),
that I can build *some* subset of
On 2020-12-02 3:50, Matthias Apitz wrote:
Thanks for all this additional clarification. In the host (where
poudriere is running) I always install some ports before running
poudriere, like
ports-mgmt/poudriere-devel
shells/bash
www/nginx
www/wget
devel/subversion
editors/vim
sysutils/tmux
You
On 2020-10-14 20:56, Robert Huff wrote:
Is anyone out there successfully using FreeBSD as a media server for
a Roku device?
Yes, with Plex Media Server. Works flawlessly, though Plex is sensitive
about its data files. Manually stopping it and snapping its data before
upgrading is key to
I want to do a poudriere bulk against 2019Q3 over the weekend, but it
appears to not exist yet? Usually the branch creation is pretty timely,
so I wanted to check to make sure I'm not missing something.
___
freebsd-ports@freebsd.org mailing list
On 2019-06-23 7:22, Carmel NY wrote:
FreeBSD 12.0-RELEASE-p6 GENERIC amd64
openssl version: OpenSSL 1.0.2s 28 May 2019
I want to use openssl111 so I can take advantage of 'tls 1.3' with
postfix and apache24. I am trying to determine the correct procedure to
use. I am using poudriere to build
On 2019-06-08 9:57, Adam Weinberger wrote:
On Sat, Jun 8, 2019 at 10:02 AM Gerald Pfeifer wrote:
In https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237688 we had
a user report against lang/gcc* ports that could be traced back to
a certain functionality (option) in another port
On Nov 27, r486043 was committed to head to fix several vulnerabilities
in the Samba 4.7 and 4.8 ports, but it wasn't merged to 2018Q4. A PR
was opened, but 2018Q4 sat unfixed until it expired at the end of the year.
Filing a PR didn't help. Mentioning the PR on this list didn't help.
What
On 2018-12-22 4:02, Kurt Jaeger wrote:
Hi!
On 2018-12-12 19:19, Mel Pilgrim wrote:
Would someone work on ports/233749, please? The original security fix
was committed to head 15 days ago, but has yet to be merged to quarterly.
I realize it's the holidays, but this is a security fix
On 2018-12-12 19:19, Mel Pilgrim wrote:
Would someone work on ports/233749, please? The original security fix
was committed to head 15 days ago, but has yet to be merged to quarterly.
I realize it's the holidays, but this is a security fix for a major port.
Or is it the plan to let this go
I only need to build a single port plus the handful of private
meta-ports I use for role management. It seems a terrible waste to have
poudriere build the 500+ completely stock dependencies they pull in. Is
there a way to have poudriere install implicitly-added pkgs from
pkg.freebsd.org
Would someone work on ports/233749, please? The original security fix
was committed to head 15 days ago, but has yet to be merged to quarterly.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
On 09/17/2018 17:52, Carmel NY wrote:
I have come across several ports that poudriere builds with the wrong
dependencies.
I have MySQL 8.0 installed by poudriere. I wanted to install
"databases/mysqlbackup" When built using the system "make install" command, it
works fine. However, when I
The mail/postfixadmin port was broken on the last update, and 231424
unbreaks it. I would like to get it into the tree ahead of the 2018Q4
branch so that quarterly users aren't affected. Would a committer
please take it?
Thank you
___
The bug has a maintainer-approved patch since April 3. Would someone
please commit this change? Thanks.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to
On 2018-04-05 12:48, Thomas Zander wrote:
Hi,
On 4 April 2018 at 11:30, Mel Pilgrim <list_free...@bluerosetech.com> wrote:
On the topic of MFH emails, were those for r453380 and r465710 (both
security updates to security/openssl with MFH tags) not sent?
Those mails were sent on Marc
On 04/04/2018 00:00, Thomas Zander wrote:
Hi,
On 2 April 2018 at 18:50, Mel Pilgrim <list_free...@bluerosetech.com> wrote:
The update to net/samba4{5,6,7} addressing CVEs went to head on March 13.
The security/openssl update to 1.0.2o was committed to head with MFH 2018Q1
explicitly
The update to net/samba4{5,6,7} addressing CVEs went to head on March
13. The security/openssl update to 1.0.2o was committed to head with
MFH 2018Q1 explicitly asked for in the commit message. In both cases,
2018Q1 expired before the MFH happened.
Last year, r453380 updated
On 2018-02-14 19:13, Janky Jay, III wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
May have spoken too soon...
On 2/14/2018 7:45 PM, Janky Jay, III wrote:
Hello Mel,
On 2/13/2018 7:42 AM, Mel Pilgrim wrote:
(Putting on my mail/postfixadmin maintainer hat)
On 2018-02-11 15:24, Janky
(Putting on my mail/postfixadmin maintainer hat)
On 2018-02-11 15:24, Janky Jay, III wrote:
Hello All,
Versions:
FreeBSD - 11.1-RELEASE-p6
PostfixAdmin - 3.1
Smarty3 - 3.1.30
Postfixadmin bundles its own copy of Smarty, and in PFA 3.1 it's Smarty
3.1.29. Installing www/smarty3 isn't
In the midst of all the negative noise, I thought I'd post and say thank
you for bring in this feature. I've been chomping at the bit to try
flavours out since I heard about them. I started flavouring my
company's internal Ports Tree extension the evening after it landed.
Flavours are going
On 12/6/2017 3:40 PM, Mel Pilgrim wrote:
The last time I had a major stability problem with FreeBSD was when I
had a brand new Nocona Xeon system that would get interrupt storms
running 5.x and had to run 6-CURRENT on it for a while because 6.x
introduced MSI support.
Or was that 4.x
On 12/5/2017 2:25 PM, 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.
I manage (currently) 104
On 12/5/2017 2:09 PM, 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 11/16/2017 11:17, Miroslav Lachman wrote:
Mel Pilgrim wrote on 2017/11/16 19:30:
I have a port that has exactly one file: an RC script provided in the
FILESDIR of the skeleton itself. I can't use metaport because I do have
to install a file.
I've had no luck finding anything
I have a port that has exactly one file: an RC script provided in the
FILESDIR of the skeleton itself. I can't use metaport because I do have
to install a file.
I've had no luck finding anything that explains how to do this, and am
meeting no end of errors when I test the port.
How do I
On 11/07/2017 07:54, Miroslav Lachman wrote:
What is the best way to maintain local ports tree changes?
I am building packages in poudriere, 4 different sets for 2 archs (8
sets in total).
I have some local ports and some changes to official ports. Now we are
planing to do some small
On 10/15/2017 11:41, Baptiste Daroussin wrote:
On Sun, Oct 15, 2017 at 06:15:24PM +, Yuri wrote:
Uses/ssl.mk allows SSL_DEFAULT=base. I know this has been discussed here
before, but why is this even allowed? If some ports are built with
SSL_DEFAULT=base, and some with SSL_DEFAULT=openssl,
On 10/11/2017 11:15, Jos Chrispijn wrote:
Dear group,
Apparently I have an issue when finalizing the ports with portmanager.
[...]
pkg: sqlite error while executing sqlite open in file pkgdb.c:1126:
unable to open database file
I checked numerous solutions, but most of them refer to a
On 10/12/2017 00:58, Guido Falsi wrote:
On 10/12/2017 01:04, Adam Weinberger wrote:
On 11 Oct, 2017, at 16:52, Mel Pilgrim <list_free...@bluerosetech.com> wrote:
Will the FLAVORS feature be MFH'd to 2017Q4, or will it first show up with
2018Q1? I'm not going to flavor public ports ju
Will the FLAVORS feature be MFH'd to 2017Q4, or will it first show up
with 2018Q1? I'm not going to flavor public ports just yet, but I have
some local ports that would benefit from the feature.
___
freebsd-ports@freebsd.org mailing list
On 09/26/2017 16:56, Greg 'groggy' Lehey wrote:
On Wednesday, 27 September 2017 at 4:39:29 +1000, Andy Farkas wrote:
On 27/09/2017 04:22, Mathieu Arnold wrote:
Please read the whole email.
What are FLAVORS and why do I need it?
Is there somewhere that explains the intent and purpose?
On 04/19/2017 22:22, Mark Linimon wrote:
On Wed, Apr 19, 2017 at 04:37:05PM -0400, scratch65...@att.net wrote:
(Right now, it's quite hard to resist the paranoid suspicion that
maybe this crazy, anti-real-user behavior is a subtle way to kill
freebsd altogether by driving away the
A PR for a port I maintain includes a patch. I'm supposed to set the
maintainer-approval flag to + to approve the patch, but it doesn't seem
to be working. When I go to the patch details page, I can set
maintainer-approval+, but it doesn't stick, even if I include a comment.
I found an older
On 01/03/2017 08:33, Miroslav Lachman wrote:
Vlad K. wrote on 2017/01/03 17:16:
I've submitted a patch for Postgres server ports with a note about
enabling checksumming
(https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=214671). I'm now
preparing to submit a patch with a similar "Nice to know"
I track the quarterly ports branches so that I can build ports from the
same tree as binary packages so that I don't, for example, have to build
all 2783 packages on my dev VM, just the 13 where I need non-default
options. Yes I know, "That is not the intended use, ma'am," blah blah
void my
On 2015-10-28 20:54, Bryan Drewery wrote:
On 10/28/2015 5:36 PM, Mel Pilgrim wrote:
Nearly every time I send a maintainer update, there's some new method I
don't know about. There's nothing about it on ports or ports-announce
and porttools/portlint don't mention it either. I end up scanning
Nearly every time I send a maintainer update, there's some new method I
don't know about. There's nothing about it on ports or ports-announce
and porttools/portlint don't mention it either. I end up scanning
through commits to ports/head/Mk to find them after the fact.
What do I need to do
I have ports/branches/2015Q4 checked out for poudrerie thinking that it
would be aligned to what's in the quarterly pkg.freebsd.org repos, but
that doesn't seem to be the case. For example, right now
pkg.freebsd.org has dovecot2-2.2.19, but the 2015Q4 branch only has
dovecot2-2.2.18.
I
On 2015-10-20 21:02, Bryan Drewery wrote:
On 10/20/2015 1:54 AM, Mel Pilgrim wrote:
I have ports/branches/2015Q4 checked out for poudrerie thinking that it
would be aligned to what's in the quarterly pkg.freebsd.org repos, but
that doesn't seem to be the case. For example, right now
On 2015-10-09 01:49, Willem Jan Withagen (ecoRacks) wrote:
Hi,
Trying to upgrade Postfix, and this is what pkg suggests:
New packages to be INSTALLED:
jpeg-turbo: 1.4.1 [zfs.digiware.nl]
mozjpeg: 3.1_1 [FreeBSD]
pth-hard: 2.0.7_1 [FreeBSD]
pkg-devel:
On 2015-09-30 16:16, Lowell Gilbert wrote:
In short, there is nothing broken in pkg(8) per se. I am pretty sure
this problem does not come up if you do everything from quarterly or
everything from head; it's strictly an issue of conflicts between the
two.
More to the point, that using the
On 2015-09-28 21:31, Kevin Oberman wrote:
On Mon, Sep 28, 2015 at 4:41 PM, Mel Pilgrim <list_free...@bluerosetech.com>
wrote:
I'm trying to build and install security/openssh-portable, but when I do,
make errors out with:
===> openssh-portable-7.1.p1_2,1 pkg(8) must be vers
On 2015-09-29 08:24, Janky Jay, III wrote:
I ran into this exact same issue using SVN and portmaster to upgrade
'git'. Upgrading 'pkg' using portmaster (portmaster -d 'pkg-1.5.6')
before running 'portmaster -ad' fixed the issue. Generally, though,
portmaster usually updates pkg first and
I'm trying to build and install security/openssh-portable, but when I
do, make errors out with:
===> openssh-portable-7.1.p1_2,1 pkg(8) must be version 1.6.0 or
greater, but you have 1.5.6. You must upgrade the ports-mgmt/pkg port first.
*** Error code 1
Stop.
make: stopped in
On 2015-07-07 11:29, Carmel NY wrote:
On Tue, 7 Jul 2015 17:06:05 +, Brooks Davis stated:
We need a port that allows dovecot2 SASL by default. There are a bunch of
turorials on setting up such systems and all of the have to start with build
everything by hand which makes us look bad.
On 2015-04-01 13:42, Mike Clarke wrote:
Where can I now obtain the revision number for the ports tree used for the
latest
package build?
Although the above method has worked in the past it's a bit of a bodge. The
ideal
way would be if this information could be accessed directly from the
46 matches
Mail list logo
