On 10/13/13 18:40, Joe Nosay wrote:
Will the pkg upgrade work with applications built from ports and not pkg
add $APPLICATION?
I'm not sure What you mean.
the "pkg upgrade" command works only using binary packages, which can
come and "official" repository or your own one.
This is going to w
On Mon, Oct 14, 2013 at 3:43 AM, Guido Falsi wrote:
> On 10/13/13 18:40, Joe Nosay wrote:
>
>> Will the pkg upgrade work with applications built from ports and not pkg
>> add $APPLICATION?
>>
>
> I'm not sure What you mean.
>
> the "pkg upgrade" command works only using binary packages, which can
On Sun, 13 Oct 2013, the wise Larry Rosenman wrote:
re-checkout the tree
I did a re-checkout but I'm still getting errors:
Updating '/usr/ports':
svn: E02: Can't open file
'/usr/ports/.svn/pristine/3d/3d137a82c6597c2c70a7f77b171e7456196e847e.svn-base':
No such file or directory
On Mon, 14 Oct 2013 10:53:56 +0200 (CEST)
Marco Beishuizen wrote:
> On Sun, 13 Oct 2013, the wise Larry Rosenman wrote:
>
> > re-checkout the tree
>
> I did a re-checkout but I'm still getting errors:
>
> Updating '/usr/ports':
> svn: E02: Can't open file
> '/usr/ports/.svn/pristi
On Mon, 14 Oct 2013, the wise Sergey V. Dyatko wrote:
rm -fr /usr/ports
svn co ..
I did this too but still no new ports tree:
root@yokozuna:/home/marco# svn co svn://svn.freebsd.org/ports/head ports
Checked out revision 330285.
root@yokozuna:/home/marco# svn up /usr/ports
Skipped '/usr/ports'
## Marco Beishuizen (mb...@xs4all.nl):
> I did this too but still no new ports tree:
>
> root@yokozuna:/home/marco# svn co svn://svn.freebsd.org/ports/head ports
> Checked out revision 330285.
Your freshly checked out ports tree now lives in /home/marco/ports
(if your line was really copy&pasted
On Mon, 14 Oct 2013, the wise Christoph Moench-Tegeder wrote:
Your freshly checked out ports tree now lives in /home/marco/ports
(if your line was really copy&pasted).
You are right. After I redid all the steps (this time the right way) all
seems well now.
Thanks for all the help!
Regards,
(Note: an HTML version of this report is available at
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=ports .)
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsol
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
No matches t
Do I understand this situation correctly:
Users are having issues with building/installing packages with STAGEDIR
enabled in lightweight jails that use symlinks to share parts of the
base system between many jails to make it easier to upgrade the jails
and avoid duplication/wasted disk space? It s
I have actually noticed many times earlier that using symlinks for
/usr/ports, /usr/src and the related directories do cause problems,
jails or not.
-Kimmo
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
- Convert to USES+=tk
- STAGE-clean
-
Build ID: 20131014130800-53018
Job owner: g...@freebsd.org
Buildtime: 2 hours
Enddate: Mon, 14 Oct 2013 15:29:13 GMT
Revision: r330316
Fix package name collision
-
Build ID: 20131014065401-5671
Job owner: b...@freebsd.org
Buildtime: 9 hours
Enddate: Mon, 14 Oct 2013 15:36:53 GMT
Revision: r330275
Repository
On Sun, Oct 13, 2013 at 9:27 AM, Dewayne
wrote:
> My setup is slightly different, where I do use as Matthew recommends,
> nullfs is used without symlinks; and pkg_* and portmaster are used for
> the build process. We've been using jails to build ports for different
> architectures for years, the
Ronald F. Guilmette wrote on 06.10.2013 01:34:
make -V FETCH_CMD
Results:
/usr/bin/fetch -AFpr
on your system? What FreeBSD version you are using?
FreeBSD segfault.tristatelogic.com 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825:
Tue Dec 4 09:23:10 UTC 2012
r...@farrell.cse.buffalo.ed
Hi,
> On Mon, 14 Oct 2013 05:49:36 GMT
> Dewayne said:
I cannot reproduce it even with openldap24-sasl-client, here.
Since this message is from bsd.ldap.mk, this PR should be assigned to
the maintainer of bsd.ldap.mk rather than individual ports such as
cyrus-sasl2-saslauthd.
Sincerely,
Synopsis: security/cyrus-sasl2-saslauthd erroneously asserts wrong openldap
version
Responsible-Changed-From-To: ume->ports
Responsible-Changed-By: ume
Responsible-Changed-When: Mon Oct 14 16:20:20 UTC 2013
Responsible-Changed-Why:
It seems this is not for individual ports.
http://www.freebsd.o
On Mon, 14 Oct 2013 20:13:51 +0400
Ruslan Makhmatkhanov wrote:
> Ronald F. Guilmette wrote on 06.10.2013 01:34:
> >
> >> make -V FETCH_CMD
> >
> > Results:
> >
> > /usr/bin/fetch -AFpr
> >
> >> on your system? What FreeBSD version you are using?
> >
> > FreeBSD segfault.tristatelogic.com 9.1-RELE
Synopsis: [PATCH] devel/liboil: Fix build with clang
Responsible-Changed-From-To: mm->ports
Responsible-Changed-By: mm
Responsible-Changed-When: Mon Oct 14 17:54:58 UTC 2013
Responsible-Changed-Why:
Reassign back to ports@ as I no longer maintain liboil
http://www.freebsd.org/cgi/query-pr.cgi?pr
The following reply was made to PR ports/182960; it has been noted by GNATS.
From: Dewayne
To: bug-follo...@freebsd.org, dewayne.gerag...@heuristicsystems.com.au
Cc:
Subject: Re: ports/182960: security/cyrus-sasl2-saslauthd erroneously asserts
wrong openldap version
Date: Tue, 15 Oct 2013 15:5
On Sun, Oct 13, 2013 at 05:53:59PM +0200, Mariusz Zaborski wrote:
> Hi there,
>
> I got some problems while compiling wmii-devel. I would like propose
> some patch to the port. It's removed dependencies of libixp port
> version and add librrary which was missing while compiling (xrender).
Thanks,
21 matches
Mail list logo
