Last month I spoke with the maintainer of mail/postfixadmin and they
agreed to let me take maintainership since, citing lack of time. I put
in a bug[1] for it, but he hasn't answered the maintainer CC yet. Can
someone please follow this up and commit the change so I can put in the
updates to
On 12/16/2014 2:51 AM, Francois Tigeot wrote:
With pg_upgrade, I found the best method to be:
- locally build the two postgres versions you're interested in from the
Postgres distfiles.
- run pg_upgrade from one of them
and don't bother with the packages.
I hadn't thought about that. I
The entry reads:
20141208:
AFFECTS: users of databases/postgresql??-(server|client)
AUTHOR: mar...@freebsd.org
PostgreSQL version 9.3 is now the default. To upgrade from a version
lower than 9.3, follow the instructions on the PostgreSQL.org website.
On 12/11/2014 11:53 PM, Matt Smith wrote:
Somebody has let me know that I made an obvious mistake in the above. I
meant that the default rcorder is to run Unbound first followed by NSD.
So to clarify I think in the default situation Unbound starts first,
contacts NSD and gets no answer because
On 11/27/2014 4:41 AM, Torsten Zuehlsdorff wrote:
Hello,
i'm nearly done with the new port. But i have a last problem.
In short the installation procedure:
- downloading the .phar file
- copying the .phar file into stagedir (because its the complete programm)
- renaming the file from
On 11/6/2014 8:35 PM, Freddie Cash wrote:
I know there was talk about it in the recent past, but has the export the
svn revision of the ports tree used to build packages feature been added
to the repo metadata? That would eliminate a lot of the issues associated
with mixing ports and packages,
On 11/4/2014 2:28 PM, Chris H wrote:
On Tue, 04 Nov 2014 13:21:31 -0800 Chris H bsd-li...@bsdforge.com wrote
gpart(8) -a gives you what you need. If it's truly as bad as all that,
mounting the ports tree on a 512k aligned slice will reduce the slack
ahem...
that was s/512k/512b/g
The issue
On 11/1/2014 2:20 AM, Matthew Seaman wrote:
However, I wonder if it wouldn't make more sense
to create one file which includes all of the other bits of port
infrastructure. This should be a text format that people can read
easily and manipulate with a text editor or standard unix tools.
On 10/31/2014 11:56 AM, Baptiste Daroussin wrote:
tijl@ spotted an interesting point, distinfo and pkg-descr files files
convenient are taking a lot of space for free, we can reduce the size of the
while ports tree by a factor 2 by simply merging them into one of the other
files (Makefile and/or
On 7/27/2014 12:30 PM, Jerry wrote:
Sun, 27 Jul 2014 15:24:21 -0400
Is there a port of the Tor web browser https://www.torproject.org/
available? The site lists one for BSD, but I would prefer to get it via the
port's system
I think the reason it isn't in ports is because it's literally just
On 6/12/2014 6:42 AM, Baptiste Daroussin wrote:
On Thu, Jun 12, 2014 at 06:11:13AM -0700, Darren Pilgrim wrote:
Is there a way to determine the ports tree revision used for the current
public pkg repo?
Right now you have no way but knowing that we take a snapshot of the ports tree
at 1am UTC
Is there a way to determine the ports tree revision used for the current
public pkg repo?
Like any moderately complex system, I have a mix of stock and custom
packages. When I go to update stuff, I'll check out the current ports
tree and fire off poudrerie to build what I need. There's a
On 6/5/2014 6:05 PM, Erich Dollansky wrote:
Hi,
On Thu, 05 Jun 2014 15:09:53 -0500
Paul Schmehl pschmehl_li...@tx.rr.com wrote:
That decided it was a good idea to completely break ports to force
people to upgrade? You couldn't come up with a warning system
instead of outright breaking ports?
On 6/3/2014 7:50 AM, Alfred Perlstein wrote:
On 6/3/14, 5:16 AM, David Chisnall wrote:
On 3 Jun 2014, at 13:09, Vitaly Magerya vmage...@gmail.com wrote:
It doesn't seem to be possible to post comments (or bugs) without creating an
account and logging in.
That is correct. The current
This is still the case. It looks like Dovecot updated to 2.2.13 and
pigeonhole to 0.4.3, and they took down the 0.4.2 distfile. Can we get
the 0.4.2 distfile hosted on ftp.freebsd.org until the maintainer
updates the ports?
On 5/15/2014 8:12 PM, Darren Pilgrim wrote:
I'm trying to update
On 4/30/2014 12:48 PM, Michael Grimm wrote:
[CC'd to freebsd-ports]
On 28.04.2014, at 00:50, Jamie Landeg-Jones ja...@dyslexicfish.net wrote:
Scot Hetzel swhet...@gmail.com wrote:
Here's a list of some that link against /lib/libcrypto.so.7 and/or
/lib/libssl.so.7
[...]
that this is clear we should be able to get this resolved.
I hate to nag about this, but can we get this fixed sometime soon? In
the three weeks since Mark's email, osa updated the port to 1.4.7, but
didn't bother fixing this issue. What happened to this being a
showstopper in a major port?
Regards,
Darren
On 3/9/2014 6:43 PM, LuKreme wrote:
# uname -a
FreeBSD ns1.covisp.net 8.4-RELEASE-p7 FreeBSD 8.4-RELEASE-p7 #0: Sat Jan 11
01:45:47 UTC 2014 root@amd64-builde
r.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
# freebsd-update -r 9.0-RELEASE fetch
Looking up update.FreeBSD.org
Can someone please look at this and commit the fix? I've had no
response and the issue means the nginx is broken for the best practices
case.
On 2/28/2014 3:09 PM, Darren Pilgrim wrote:
A recent change to the www/nginx Makefile broke the port for the case
where you have the OpenSSL port
On 3/6/2014 3:07 PM, Mark Felder wrote:
Hi Darren,
I'm trying to understand exactly what we're looking at here. Is the
problem:
nginx always builds against OpenSSL in base (for FreeBSD 10+?) ?
If so, that's correct; it should not build against OpenSSL from ports
just because the version from
A recent change to the www/nginx Makefile broke the port for the case
where you have the OpenSSL port installed on FreeBSD 10. The breakage
is due to incorrectly setting WITH_OPENSSL_BASE and the fix is to remove
two lines in the Makefile:
--- Makefile.old2014-01-30
I'm running into pkgng errors on all of my systems:
# pkg update -f
Updating repository catalogue
digests.txz 100% 1081KB
1.1MB/s 1.1MB/s 00:00
packagesite.txz 100% 5037KB
4.9MB/s 4.9MB/s 00:01
I just retired the last of my 3ware hardware and as such can no longer
do the basic functionality testing required. The port has special
distfiles I host. I can continue to host them indefinitely, but it
would likely be easier if the new maintainer took over hosting them.
Is there someone
On 11/16/2013 8:25 AM, Eitan Adler wrote:
On Sat, Nov 16, 2013 at 10:19 AM, Melvyn Sopacua mel...@magemana.nl wrote:
2) If meta-information is moved to pkg-descr, it might be worthwhile
to add some knowledge about formats and restrictions to portlint.
If we go this route I would *strongly*
On 11/16/2013 2:08 PM, Eitan Adler wrote:
On Sat, Nov 16, 2013 at 2:41 PM, Darren Pilgrim
list_free...@bluerosetech.com wrote:
On 11/16/2013 8:25 AM, Eitan Adler wrote:
That's parseable using the regex or literal matching built into every
scripting language, most programming languages, and your
On 11/13/2013 3:15 PM, Joe Nosay wrote:
ls -lh -D Byte does not give me the exact byte size of the archive. What
is the correct command?
The makesum target will create distinfo for you.
___
freebsd-ports@freebsd.org mailing list
Now that we have a repo, I want to start using binary packages for the
numerous dependencies I have to install on pretty much every system:
autotools, ca_root_nss, cmake-modules, gettext, glib, libtool, m4, etc.
But `pkg upgrade` only asks me to upgrade everything at once. This
absolutely
Would someone commit this please?
Thanks
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
On 9/11/2013 1:01 AM, Baptiste Daroussin wrote:
A quick fix here is to mark squirrelmail as not package friendly for now.
Do you want me to do that?
# make -C /usr/ports/mail/squirrelmail maintainer
ad...@freebsd.org
You're asking the wrong person.
On 9/5/2013 9:00 PM, Aryeh Friedman wrote:
related questions:
1. How do I add the user to wheel (has it's own group but needs to be in
wheel for reason number #2)?
2. How do I modify (in the safest possible way) an other port's installed
config file(s) (namely I need to in the case of this port
On 9/5/2013 6:52 PM, Aryeh Friedman wrote:
I have a port that needs to create a a user of a given name and a given
default password... I found in the porters guide how to make the account
but not set the password
Because you must not do that. You can't even reliably do that. There
are many
My port: mail/squirrelmail-postfixadmin-plugin
Over the last two days I have received five Build failed messages from
pkg-fallout, one each for {83,91}{amd64,i386} and head. The messages
are quite long, but the juicy bits are below. The [...] indicates a
gap in the log.
On 2013-04-08 08:26, Freddie Cash wrote:
The really hard part is coming up with a migration path for those who
upgrade via source builds.
It already exists:
1. Update to release that doesn't include $thing;
2. make -C /usr/src delete-old delete-old-libs;
3. Install $thing or
On 2013-04-08 10:22, Florent Peterschmitt wrote:
Yep, OpenSSH is tiny enought to keep it in base system. It would be a
big loss not to have it by default, securely installed in the base
system.
I really wish it wasn't. Having OpenSSH (and thus OpenSSL) in the base
means FreeBSD has an
With pkg_info, I can get a list of ports requiring and depended on by a
given port by doing `pkg_info -rR`. In pkgNG, the equivalent would be
`pkg info -dr`, but there appears to be a problem giving -d and -r at
the same time. For example:
# pkg info -r postgresql-client-9.2.3
It was approved by the maintainer a week ago, but hasn't been committed
yet. If someone would pick this one up soon it would be appreciated,
thanks.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To
On 2013-02-20 19:08, andrew clarke wrote:
On Wed 2013-02-20 17:45:52 UTC-0800, Darren Pilgrim
(list_free...@bluerosetech.com) wrote:
Reading the pkgng page on the wiki:
As a consequence of the security incident on 11th November 2012, for
the time being pre-compiled packages for pkgng
Setting up a new server tonight, decided to do it up with pkgng from the
start:
1. portsnapped a tree
2. installed pkg just fine from ports
3. added WITH_PKGNG=yes to /etc/make.conf
4. cp /usr/local/etc/pkg.conf.sample /usr/local/etc/pkg.conf
Then it broke:
# pkg update
Updating repository
On 2013-02-20 18:19, meta wrote:
Probably, the repository is pkgbeta.freebsd.org currently.
You just type `pkg` before installing pkg from ports pkg bootstrap
runs.
If you install pkg in this way, 'pkgbeta.freebsd.org' is written in
pkg.conf .
pkgbeta just has pkg and poudriere in it, though.
On 2013-02-16 08:06, Chris Rees wrote:
I think you may have some luck installing an up to date make(1) and
dialog(1) (or set NO_DIALOG=yes in make.conf) from stable/9 or
similar; many of the problems on 6 are caused by missing variable
modifiers.
I built and installed make from a RELENG_8_3
On 2013-02-18 16:22, Darren Pilgrim wrote:
On 2013-02-16 08:06, Chris Rees wrote:
I think you may have some luck installing an up to date make(1) and
dialog(1) (or set NO_DIALOG=yes in make.conf) from stable/9 or
similar; many of the problems on 6 are caused by missing variable
modifiers.
I
I have an old 6.4-R machine which I can take as far as RELENG_6, but no
further due to a hardware-support issue (special hardware, third party
driver). The hardware needs to live a while yet, so I'd like to try to
get the installed ports as up to date as possible. The current ports
tree
On 2013-02-16 08:06, Chris Rees wrote:
I'm pretty certain that ports on 6.X was broken with OPTIONSng
(r297660), but I seem to remember that other compatibility was ripped
out before then; perhaps Mark can clarify.
r259629 specifically talks about removing 6.3 shims, but that is way before.
On 2012-06-15 14:25, Robert Simmons wrote:
On Fri, Jun 15, 2012 at 5:11 PM, Rich Neeser.ne...@gmail.com wrote:
I just wish skype would get off their buts and make a bsd version. time
to break code and make a opensource version
That's not the answer. Really, everyone needs to move away from
On 2011-11-04 10:32, David Southwell wrote:
If the following lines appear in main.cf
check_policy_service unix:private/policyd-spf
spf-policyd_time_limit = 3600s
In the following context
smtpd_recipient_restrictions = permit_mynetworks,reject_unauth_destination
check_policy_service
Paul Schmehl wrote:
I'm working on a port update for one of the ports that I maintain, and I've run
into a problem that I can't seem to solve.
I use this construction to ensure that the port doesn't overwrite the conf
file, if one exists:
.for f in barnyard2.conf
${INSTALL_DATA}
I need testers for an update to the sysutils/3dm port. If you want to
help test the patch, begin by downloading it from here:
http://vivi.cat.pdx.edu/3dm2/sysutils_3dm.patch.txt
You can apply the patch by issuing the command:
cd /usr/ports/sysutils/3dm patch /path/to/sysutils_3dm.patch.txt
I maintain the sysutils/3dm port. The port installs a binary-only
package provided by 3ware (now LSI). The binary provided is a 5.4-R,
static-linked binary which requires KSE. Because it's static-linked,
there is no legacy KSE support workaround.
Yes, LSI is aware of the problem.
No, they
Wesley Shields wrote:
On Sun, Apr 25, 2010 at 04:51:04PM -0700, Darren Pilgrim wrote:
Detect the OS version, install the latest version if running 8.x and
install 2.01.09.004 if =8.x. I can't find anything in the Porter's
Handbook that explicitly says NOT to do this. Wesley Shields (wxs
Wesley Shields wrote:
On Sat, Feb 13, 2010 at 07:26:39PM -0800, Darren Pilgrim wrote:
I'm working on a revision to a port where the current version doesn't
work on 8.0-R; however, an older version does. Rather than roll the
entire port back to an older version, I'd like to have the newer
Garrett Cooper wrote:
Vendor provided binaries are a fun ball of wax to deal with
because you need to have all dependencies come from the same generic
pool as the package [/ port] itself, as any
This sounds trivial, but it requires changes to pkg_add (for
fetching / installing a
I'm working on a revision to a port where the current version doesn't
work on 8.0-R; however, an older version does. Rather than roll the
entire port back to an older version, I'd like to have the newer version
available to 7.x and older and the older version available to 8.x and
newer. Is
I have a port which uses a static-linked 5.4 binary. This is broken in
8.0 due to KSE removal. I need to create a test and limit installation
to only those versions on which it will run.
Looking at the heads-up message for KSE removal from March 2008, I don't
see a change to
I've updated the 3dm port and need people with 32- and 64-bit 7.x and
8.x systems to test the new version. A 3ware RAID controller is
required, of course. Reply to me privately and I will email the patch.
___
freebsd-ports@freebsd.org mailing list
Xin LI wrote:
Darren Pilgrim wrote:
Tonight I source-upgraded a FreeBSD system from i386 6.3p5 to i386
6.4-R. I have postfix 2.5.5 and dovecot 1.1.7 installed with postfix
using dovecot for SASL and dovecot LDA for mailbox delivery. After
installing 6.4-R, postfix refused to work until I
I updated my ports tree today and pkg_version tells me:
php5-pcre-5.2.6_2 succeeds index (index has 5.2.5)
Which was caused by an out-of-date index. When I run make index:
Generating INDEX-6 - please wait..pear-File_Archive-1.5.4:
/data/sys/ports/devel/php5-pcre
Wesley Shields wrote:
Take a look at UPDATING, specifically the 20081211 entry.
Yeah. What's funny is, I habitually read {src,ports}/UPDATING. Must be
too much egg nog. :) Thanks.
___
freebsd-ports@freebsd.org mailing list
out and we build
amazing bike-sheds, but there has seldom been real product. What
you have yet to do is distinguish yourself from history.
In short, patches please. Until then, don't expect enthusiastic
encouragement.
--
Darren Pilgrim
The PR is regarding sysutils/3dm, a port for which I'm the maintainer.
After working with Craig (the PR submitter), I've submitted a follow-up
to the PR containing a commitable version of the suggested changes plus
a few of my own. If someone with a commit bit would be so kind, that
would be
Andriy Babiy wrote:
I wanted to try making the port, but faced a problem:
The requested URL /spca50x/Download/gspcav1-20070110.tar.gz was not found
on this server.
Apache/ProXad [Apr 14 2007 12:48:55] Server at mxhaard.free.fr
This is what I get when I try downloading the source.
Of course,
only with fam and not with gamin. But I
not certain this is still the case now. Does anyone know if latest
gamin is compatible with Courier products?
As of Monday (March 19), courier-imap crashes when compiled with gamin.
--
Darren Pilgrim
___
freebsd
Alejandro Pulver wrote:
On Sat, 10 Feb 2007 13:27:42 -0800
Darren Pilgrim [EMAIL PROTECTED] wrote:
I'm writing a port for a script that stores the configuration data in
the same file as the program code itself. The long-term solution is to
move the configuration data to another file
I'm writing a port for a script that stores the configuration data in
the same file as the program code itself. The long-term solution is to
move the configuration data to another file, of course; however, that's
proving to be a far slower process than originally expected.
Other than
net/iwi-firmware:
cd /usr/ports/net/iwi-firmware make config
Uncheck the MODULE option.
Re-run the portinstall command.
--
Darren Pilgrim
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo
Florent Thoumie wrote:
On Wed, 2006-08-23 at 13:35 -0700, Darren Pilgrim wrote:
Re net/iwi-firmware-kmod:
Don't use the iwi-firmware-kmod port, it's deprecated.
Not really, it's the one to use with HEAD and fresh RELENG_6.
Sorry, yeah, I missed the MIN6OSVERSION and MIN7OSVERSION
65 matches
Mail list logo
