date:20120821

On 8/21/2012 1:08 PM, Warner Losh wrote:
> 
> On Aug 21, 2012, at 1:51 PM, Doug Barton wrote:
> 
>> On 8/21/2012 12:42 PM, Baptiste Daroussin wrote:
>>> On Tue, Aug 21, 2012 at 12:38:04PM -0700, Doug Barton wrote:
 On 8/21/2012 12:05 PM, Baptiste Daroussin wrote:
> 1/ if it fits the schedule: get rid of pkg_* tools in
> current to be able to have a fully pkgng only 10-RELEASE

 I think it would fit better with historic precedents to make
 pkg optional (but default on) in 10, and mandatory in 11. As
 stated before, I'm fine with removing pkg_* tools from 10 if
 there is robust support for them in the ports tree.

 I know you're excited about this project, but let's not lose 
 sight of how big a change this is, and how important ports are
 to the project.

>>> That was what "if it fits the schedule" was about.
>> 
>> I think what I'm trying to say, ever so politely, is that what
>> you're suggesting isn't even an option, so it shouldn't be
>> discussed.
> 
> If you are fine with removing them if there's robust support, how can
> you also be suggesting that it is impossible and shouldn't be talked
> about?

Those address different parts of the problem. Making pkg mandatory in 10
is different from where the old pkg_* tools end up. The command line
tools are just the tip of the iceberg, there are a lot of interactions
behind the scenes.

> Personally, I think we should handle this the same way that other
> replacement tools have been done, which is close to what Baptiste has
> proposed.  If the new tools are totally awesome, we have replaced old
> tools. 

I don't think we have ever done a complete replacement of major
infrastructure in one release. The traditional model has been to
deprecate in one release, remove in the next.

And in this case, it doesn't matter how awesome the new tools are, they
are a MAJOR paradigm shift for how users interact with ports, and we are
going to have a lot of users who take years to transition their
installed base. No matter how much we may want to move fast on this, it
just isn't going to be possible.

> If the new tools are good, but don't cover the older users,
> we develop along size. 

Yes, this is precisely what I'm saying. Sorry if I wasn't clear.

-- 

I am only one, but I am one.  I cannot do everything, but I can do
something.  And I will not let what I cannot do interfere with what
I can do.
-- Edward Everett Hale, (1822 - 1909)
___
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"

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

2012-08-21 Thread Warner Losh

On Aug 21, 2012, at 1:51 PM, Doug Barton wrote:

> On 8/21/2012 12:42 PM, Baptiste Daroussin wrote:
>> On Tue, Aug 21, 2012 at 12:38:04PM -0700, Doug Barton wrote:
>>> On 8/21/2012 12:05 PM, Baptiste Daroussin wrote:
 1/ if it fits the schedule: get rid of pkg_* tools in current
 to be able to have a fully pkgng only 10-RELEASE
>>> 
>>> I think it would fit better with historic precedents to make pkg 
>>> optional (but default on) in 10, and mandatory in 11. As stated 
>>> before, I'm fine with removing pkg_* tools from 10 if there is
>>> robust support for them in the ports tree.
>>> 
>>> I know you're excited about this project, but let's not lose
>>> sight of how big a change this is, and how important ports are to
>>> the project.
>>> 
>> That was what "if it fits the schedule" was about.
> 
> I think what I'm trying to say, ever so politely, is that what you're
> suggesting isn't even an option, so it shouldn't be discussed.

If you are fine with removing them if there's robust support, how can you also 
be suggesting that it is impossible and shouldn't be talked about?

Personally, I think we should handle this the same way that other replacement 
tools have been done, which is close to what Baptiste has proposed.  If the new 
tools are totally awesome, we have replaced old tools.  If the new tools are 
good, but don't cover the older users, we develop along size.  If they are 
lame, but somehow get committed anyway, we take 18 years to replace them with 
bsdinstall.

Warner

___
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"

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

On 8/21/2012 12:42 PM, Baptiste Daroussin wrote:
> On Tue, Aug 21, 2012 at 12:38:04PM -0700, Doug Barton wrote:
>> On 8/21/2012 12:05 PM, Baptiste Daroussin wrote:
>>> 1/ if it fits the schedule: get rid of pkg_* tools in current
>>> to be able to have a fully pkgng only 10-RELEASE
>> 
>> I think it would fit better with historic precedents to make pkg 
>> optional (but default on) in 10, and mandatory in 11. As stated 
>> before, I'm fine with removing pkg_* tools from 10 if there is
>> robust support for them in the ports tree.
>> 
>> I know you're excited about this project, but let's not lose
>> sight of how big a change this is, and how important ports are to
>> the project.
>> 
> That was what "if it fits the schedule" was about.

I think what I'm trying to say, ever so politely, is that what you're
suggesting isn't even an option, so it shouldn't be discussed.


-- 

I am only one, but I am one.  I cannot do everything, but I can do
something.  And I will not let what I cannot do interfere with what
I can do.
-- Edward Everett Hale, (1822 - 1909)
___
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"

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

On Tue, Aug 21, 2012 at 12:38:04PM -0700, Doug Barton wrote:
> On 8/21/2012 12:05 PM, Baptiste Daroussin wrote:
> > 1/ if it fits the schedule: get rid of pkg_* tools in current to be
> > able to have a fully pkgng only 10-RELEASE
> 
> I think it would fit better with historic precedents to make pkg
> optional (but default on) in 10, and mandatory in 11. As stated
> before, I'm fine with removing pkg_* tools from 10 if there is robust
> support for them in the ports tree.
> 
> I know you're excited about this project, but let's not lose sight of
> how big a change this is, and how important ports are to the project.
> 
That was what "if it fits the schedule" was about.

regards,
Bapt


pgprmJFWctomi.pgp
Description: PGP signature

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

On 8/21/2012 12:05 PM, Baptiste Daroussin wrote:
> 1/ if it fits the schedule: get rid of pkg_* tools in current to be
> able to have a fully pkgng only 10-RELEASE

I think it would fit better with historic precedents to make pkg
optional (but default on) in 10, and mandatory in 11. As stated
before, I'm fine with removing pkg_* tools from 10 if there is robust
support for them in the ports tree.

I know you're excited about this project, but let's not lose sight of
how big a change this is, and how important ports are to the project.

Doug

-- 

I am only one, but I am one.  I cannot do everything, but I can do
something.  And I will not let what I cannot do interfere with what
I can do.
-- Edward Everett Hale, (1822 - 1909)
___
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"

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

On Tue, Aug 21, 2012 at 11:47:36AM -0700, Garrett Cooper wrote:
> On Tue, Aug 21, 2012 at 11:17 AM, Doug Barton  wrote:
> > On 8/21/2012 6:46 AM, Baptiste Daroussin wrote:
> >> I would also like to just remove pkg_* tools from RELENG_10 if that fits 
> >> the
> >> schedule.
> >
> > Um, no?
> 
> ...
> 
> > What _would_ be useful is what should have been done many years ago when
> > it was first suggested: Move the pkg_* tools to ports.
> 
> It already exists -- it's just out of date / crufty:
> 
> $ make describe
> pkg_install-20090902|/usr/ports/ports-mgmt/pkg_install|/usr/local|FreeBSD
> -STABLE version of the package
> tools|/usr/ports/ports-mgmt/pkg_install/pkg-descr|port...@freebsd.org|ports-mgmt||http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/pkg_install/
> 
> > It's too late for 9.1 already, but if you made that change today in
> > HEAD, and after 9.1 (but before 8.4) you MFC it to stable/[89], then you
> > could theoretically make pkg mandatory after 9.1 EOLs.
> >
> > To make my point more clear, the ports tree has to support the last
> > release to ship with pkg_* tools in the base throughout its lifetime. To
> > do anything else would be be a massive POLA violation.
> 
> Agreed.
> Thanks,
> -Garrett

Let's rephrase the plan:

1/ if it fits the schedule: get rid of pkg_* tools in current to be able to have
a fully pkgng only 10-RELEASE
2/ switch 9.2 (the ports tree) to pkgng (but keep pkg_* tools maybe drop them,
but that is to be discussed to avoid POLA
3/ do the same for 8

once all of our supported release are fully pkgng aware and all the pkg_*
release are EOLed, drop support for pkg_* tools from the ports tree.

regards,
Bapt


pgppZLkb3vyvU.pgp
Description: PGP signature

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

On 8/21/2012 11:47 AM, Garrett Cooper wrote:
> On Tue, Aug 21, 2012 at 11:17 AM, Doug Barton  wrote:
>> On 8/21/2012 6:46 AM, Baptiste Daroussin wrote:
>>> I would also like to just remove pkg_* tools from RELENG_10 if that fits the
>>> schedule.
>>
>> Um, no?
> 
> ...
> 
>> What _would_ be useful is what should have been done many years ago when
>> it was first suggested: Move the pkg_* tools to ports.
> 
> It already exists -- it's just out of date / crufty:

Right ... I was using "move" as shorthand for several different ideas,
including but not limited to the latest version of the code itself,
robust support for the code going forward, the primary supported way of
using pkg_*, etc. All of these ideas have been discussed in the past, so
I was hoping to avoid having to re-discuss them. :)

>> It's too late for 9.1 already, but if you made that change today in
>> HEAD, and after 9.1 (but before 8.4) you MFC it to stable/[89], then you
>> could theoretically make pkg mandatory after 9.1 EOLs.
>>
>> To make my point more clear, the ports tree has to support the last
>> release to ship with pkg_* tools in the base throughout its lifetime. To
>> do anything else would be be a massive POLA violation.
> 
> Agreed.

Great (and I saw Baptiste's response on this as well). Glad to hear that
we're on the same page about something at least. :)


-- 

I am only one, but I am one.  I cannot do everything, but I can do
something.  And I will not let what I cannot do interfere with what
I can do.
-- Edward Everett Hale, (1822 - 1909)
___
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"

Something wrong with mirror.irssi.org? (Was: Re: svn commit: r302888 - head/irc/irssi-devel)

2012-08-21 Thread Yuri Pankov


On Tue, 21 Aug 2012 18:48:59 + (UTC), Beat Gaetzi wrote:

Author: beat
Date: Tue Aug 21 18:48:59 2012
New Revision: 302888
URL: http://svn.freebsd.org/changeset/ports/302888

Log:
   - Mark BROKEN: size mismatch
 fetch: http://mirror.irssi.org/snapshots/irssi-20120624.tar.gz:
 size mismatch: expected 1331265, actual 1331625

   Reported by: pointyhat

Modified:
   head/irc/irssi-devel/Makefile

Modified: head/irc/irssi-devel/Makefile
==
--- head/irc/irssi-devel/Makefile   Tue Aug 21 18:46:31 2012
(r302887)
+++ head/irc/irssi-devel/Makefile   Tue Aug 21 18:48:59 2012
(r302888)
@@ -16,6 +16,8 @@ COMMENT=  A modular IRC client with many

  LIB_DEPENDS=  glib-2.0:${PORTSDIR}/devel/glib20

+BROKEN=size mismatch
+
  CONFLICTS=irssi-0.8*

  GNU_CONFIGURE=yes


I've filed this as 170541, but it looks like filesize changes every now 
and then (something wrong with mirror.irssi.org?).

___
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"

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

2012-08-21 Thread Garrett Cooper

On Tue, Aug 21, 2012 at 11:17 AM, Doug Barton  wrote:
> On 8/21/2012 6:46 AM, Baptiste Daroussin wrote:
>> I would also like to just remove pkg_* tools from RELENG_10 if that fits the
>> schedule.
>
> Um, no?

...

> What _would_ be useful is what should have been done many years ago when
> it was first suggested: Move the pkg_* tools to ports.

It already exists -- it's just out of date / crufty:

$ make describe
pkg_install-20090902|/usr/ports/ports-mgmt/pkg_install|/usr/local|FreeBSD
-STABLE version of the package
tools|/usr/ports/ports-mgmt/pkg_install/pkg-descr|port...@freebsd.org|ports-mgmt||http://www.freebsd.org/cgi/cvsweb.cgi/src/usr.sbin/pkg_install/

> It's too late for 9.1 already, but if you made that change today in
> HEAD, and after 9.1 (but before 8.4) you MFC it to stable/[89], then you
> could theoretically make pkg mandatory after 9.1 EOLs.
>
> To make my point more clear, the ports tree has to support the last
> release to ship with pkg_* tools in the base throughout its lifetime. To
> do anything else would be be a massive POLA violation.

Agreed.
Thanks,
-Garrett
___
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"

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

On Tue, Aug 21, 2012 at 11:17:36AM -0700, Doug Barton wrote:
> On 8/21/2012 6:46 AM, Baptiste Daroussin wrote:
> > I would also like to just remove pkg_* tools from RELENG_10 if that fits the
> > schedule.
> 
> Um, no?
> 
> Until pkg becomes mandatory (which can't happen for several years) the
> pkg_* tools can't be removed altogether.
> 
> What _would_ be useful is what should have been done many years ago when
> it was first suggested: Move the pkg_* tools to ports.
> 
> It's too late for 9.1 already, but if you made that change today in
> HEAD, and after 9.1 (but before 8.4) you MFC it to stable/[89], then you
> could theoretically make pkg mandatory after 9.1 EOLs.
> 
> To make my point more clear, the ports tree has to support the last
> release to ship with pkg_* tools in the base throughout its lifetime. To
> do anything else would be be a massive POLA violation.
> 
> Doug
> 
> -- 
> 
> I am only one, but I am one.  I cannot do everything, but I can do
> something.  And I will not let what I cannot do interfere with what
> I can do.
>   -- Edward Everett Hale, (1822 - 1909)

that is what I meant of course, sorry if I badly said it at first

Bapt


pgpu5pCBh5GW0.pgp
Description: PGP signature

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

On 8/21/2012 6:46 AM, Baptiste Daroussin wrote:
> I would also like to just remove pkg_* tools from RELENG_10 if that fits the
> schedule.

Um, no?

Until pkg becomes mandatory (which can't happen for several years) the
pkg_* tools can't be removed altogether.

What _would_ be useful is what should have been done many years ago when
it was first suggested: Move the pkg_* tools to ports.

It's too late for 9.1 already, but if you made that change today in
HEAD, and after 9.1 (but before 8.4) you MFC it to stable/[89], then you
could theoretically make pkg mandatory after 9.1 EOLs.

To make my point more clear, the ports tree has to support the last
release to ship with pkg_* tools in the base throughout its lifetime. To
do anything else would be be a massive POLA violation.

Doug

-- 

I am only one, but I am one.  I cannot do everything, but I can do
something.  And I will not let what I cannot do interfere with what
I can do.
-- Edward Everett Hale, (1822 - 1909)
___
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"

Re: pkg(ng)/portupgrade-devel: does not respect setting of USE_GCC= 4.6+

2012-08-21 Thread O. Hartmann

Am 08/21/12 11:25, schrieb Andrew W. Nosenko:
> On Mon, Aug 20, 2012 at 10:39 PM, O. Hartmann
>  wrote:
>> I'm pretty sure, that the last time I updated port math/fftw3 I wanted
>> option OpenMP enabled so I declared "USE_GCC=4.6+" in make.conf. Later,
>> also working!, I excluded all these user definitions into an external
>> file called ports.conf located in /usr/local/etc (I like this clean
>> separation of OS and user messes ;-) ). Suddenly it doesn't work
>> anymore. There were changes in several Mk files located in /usr/ports/Mk.
> 
> Beware!  Even if you will be able to force gcc-4.6 to be used and thus
> obtain OpenMP-3.1 at the compilation stage, the libgomp.so.1, which
> will be used at run-time, will be OpenMP-3.0 from the base gcc-4.2
> (/usr/lib/libgomp.so.1 on my FreeBSD-8.0 system).  Also, as a bonus,

Shouldn't that be /usr/local/lib/gcc46/libgomp.so.1 then? If not, then
using a modern and fast compiler like gcc 4.6/4.7 or even 4.8 for OMP is
useless on FreeBSD (I use FreeBSD 9.1-PRE and 10.0-CURRENT).

> you may be exposed to ancient bugs from the gcc-4.2 openmp
> implementation.  For me, personally, it is memory leak as described in
> http://gcc.gnu.org/ml/gcc/2009-05/msg00427.html
> Fixed in gcc-4.3, but gcc-4.3 never was nor will be in base.
> 
> Thus...  For obtain the proper openmp you will either limit yourself
> to openmp-3.0 from gcc-4.2 and workaround known bugs, or make a black
> magic dance for override and "unsteal" the libgomp (e.g. using
> libmap.conf) and have maintenance problem every time when gcc version
> changes (and, therefore, changes the directory name, where gcc
> libraries live).

Well, I see, here comes the black magic in refering eventually to
/usr/local/lib/gcc46/libgomp.so.1.

I'm confused now! I try avoiding the lagcy and outdated gcc 4.2.
Unfortunatelly, CLANG doesn't support OpenMP (yet), and it is not clear
when OpenMP will ever make in in due time into it.

I thought, and this seems to be a big mistake and misunderstanding of
mine, that USE_GCC=4.6+ will circumvent any problems and even relocated
the library paths for compiled software using OpenMP.

We use lots of modelling software based upon OpenMP. That would imply if
still using USE_GCC=4.6+ to provide OpenMP support will reel in the
outdated libgomp.so.1 from the legacy gcc4.2?

this is a very bad outlook ...

> 

signature.asc
Description: OpenPGP digital signature

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

2012-08-21 Thread Kimmo Paasiala

On Tue, Aug 21, 2012 at 6:26 PM, Kimmo Paasiala  wrote:
> On Tue, Aug 21, 2012 at 5:45 PM, Lawrence Stewart  
> wrote:
>> On 08/21/12 17:04, Baptiste Daroussin wrote:
>>> On Tue, Aug 21, 2012 at 07:05:49AM +0100, Matthew Seaman wrote:
 On 21/08/2012 00:21, Baptiste Daroussin wrote:
> On Tue, Aug 21, 2012 at 12:09:46AM +0300, Vitaly Magerya wrote:
>> Baptiste Daroussin  wrote:
>>> Please [...] ask question about pkgng [...]
>>
>> What would be the best practice of mixing ports with packages?
>>
>> The use case I have in mind is compiling Xorg ports locally
>> WITH_NEW_XORG and WITH_KMS, and using packages from
>> pkgbeta.freebsd.org for everything else. Is there some mixture of pkg
>> and portmaster flags that allows this kind of setup?
>> ___
>> 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"
>
> There is no best practice for that unfortunatly, (as actually) the best 
> for you
> is maybe to build your own pkgng repostories?
> http://wiki.freebsd.org/PkgPrimer#Using_poudriere for example?
>
> We are open to suggestion here :)

 At the moment, it is about as tricky as mixing locally compiled ports
 with pkg_tools packages: ie. it might work, or it might leave you a
 quivering, sobbing mess lost in a pit of dark despair.

 One thing that should help is a proposal to record metadata like the SVN
 revision number of the ports tree used to build repository packages into
 the repository catalogue (repo.sqlite), so users can in principle check
 out the same revision locally to build their own ports.  Unfortunately
 no one has written that yet, and its probably too late for it to make it
 into release-1.0.

>>>
>>> yes but it should definitly find its way to 1.1!
>>
>>
>> Agreed, though ultimately we want to move to making mixing of ports &
>> pkgs idiot-proof - something I suspect we're in better shape to do with
>> pkgng. As a recently minted roadtester of pkgng and wanting to do the
>> same as Vitaly without setting up Poudriere, I had to reverse engineer
>> the ports tree svn revision to make sure I could mix and match from
>> pkgbeta and stuff I built locally via ports with WITH_NEW_XORG and
>> WITH_KMS. This becomes more annoying to manage going forward.
>>
>> So far I'm enjoying my pkgng experience for the most part and wish to
>> thank all those involved in getting it to this stage.
>>
>> Cheers,
>> Lawrence
>
> What would be needed is a mechanism to query a package repository for
> a package with both name and options  used to compile the package.
> Let's say you have a port installed that requires another port but
> that other port must be compiled with a certain option turned on. The
> packaging system should be able to tell if the package available from
> the remote repository satisfies the requirements or not. The current
> system accepts any version of the package because it only looks at the
> package name.

By 'any version' I mean 'a package with any combination of options' of
course, bad wording.

-Kimmo
___
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"

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

2012-08-21 Thread Kimmo Paasiala

On Tue, Aug 21, 2012 at 5:45 PM, Lawrence Stewart  wrote:
> On 08/21/12 17:04, Baptiste Daroussin wrote:
>> On Tue, Aug 21, 2012 at 07:05:49AM +0100, Matthew Seaman wrote:
>>> On 21/08/2012 00:21, Baptiste Daroussin wrote:
 On Tue, Aug 21, 2012 at 12:09:46AM +0300, Vitaly Magerya wrote:
> Baptiste Daroussin  wrote:
>> Please [...] ask question about pkgng [...]
>
> What would be the best practice of mixing ports with packages?
>
> The use case I have in mind is compiling Xorg ports locally
> WITH_NEW_XORG and WITH_KMS, and using packages from
> pkgbeta.freebsd.org for everything else. Is there some mixture of pkg
> and portmaster flags that allows this kind of setup?
> ___
> 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"

 There is no best practice for that unfortunatly, (as actually) the best 
 for you
 is maybe to build your own pkgng repostories?
 http://wiki.freebsd.org/PkgPrimer#Using_poudriere for example?

 We are open to suggestion here :)
>>>
>>> At the moment, it is about as tricky as mixing locally compiled ports
>>> with pkg_tools packages: ie. it might work, or it might leave you a
>>> quivering, sobbing mess lost in a pit of dark despair.
>>>
>>> One thing that should help is a proposal to record metadata like the SVN
>>> revision number of the ports tree used to build repository packages into
>>> the repository catalogue (repo.sqlite), so users can in principle check
>>> out the same revision locally to build their own ports.  Unfortunately
>>> no one has written that yet, and its probably too late for it to make it
>>> into release-1.0.
>>>
>>
>> yes but it should definitly find its way to 1.1!
>
>
> Agreed, though ultimately we want to move to making mixing of ports &
> pkgs idiot-proof - something I suspect we're in better shape to do with
> pkgng. As a recently minted roadtester of pkgng and wanting to do the
> same as Vitaly without setting up Poudriere, I had to reverse engineer
> the ports tree svn revision to make sure I could mix and match from
> pkgbeta and stuff I built locally via ports with WITH_NEW_XORG and
> WITH_KMS. This becomes more annoying to manage going forward.
>
> So far I'm enjoying my pkgng experience for the most part and wish to
> thank all those involved in getting it to this stage.
>
> Cheers,
> Lawrence

What would be needed is a mechanism to query a package repository for
a package with both name and options  used to compile the package.
Let's say you have a port installed that requires another port but
that other port must be compiled with a certain option turned on. The
packaging system should be able to tell if the package available from
the remote repository satisfies the requirements or not. The current
system accepts any version of the package because it only looks at the
package name.
___
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"

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

2012-08-21 Thread Lawrence Stewart

On 08/21/12 17:04, Baptiste Daroussin wrote:
> On Tue, Aug 21, 2012 at 07:05:49AM +0100, Matthew Seaman wrote:
>> On 21/08/2012 00:21, Baptiste Daroussin wrote:
>>> On Tue, Aug 21, 2012 at 12:09:46AM +0300, Vitaly Magerya wrote:
 Baptiste Daroussin  wrote:
> Please [...] ask question about pkgng [...]

 What would be the best practice of mixing ports with packages?

 The use case I have in mind is compiling Xorg ports locally
 WITH_NEW_XORG and WITH_KMS, and using packages from
 pkgbeta.freebsd.org for everything else. Is there some mixture of pkg
 and portmaster flags that allows this kind of setup?
 ___
 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"
>>>
>>> There is no best practice for that unfortunatly, (as actually) the best for 
>>> you
>>> is maybe to build your own pkgng repostories?
>>> http://wiki.freebsd.org/PkgPrimer#Using_poudriere for example?
>>>
>>> We are open to suggestion here :)
>>
>> At the moment, it is about as tricky as mixing locally compiled ports
>> with pkg_tools packages: ie. it might work, or it might leave you a
>> quivering, sobbing mess lost in a pit of dark despair.
>>
>> One thing that should help is a proposal to record metadata like the SVN
>> revision number of the ports tree used to build repository packages into
>> the repository catalogue (repo.sqlite), so users can in principle check
>> out the same revision locally to build their own ports.  Unfortunately
>> no one has written that yet, and its probably too late for it to make it
>> into release-1.0.
>>
> 
> yes but it should definitly find its way to 1.1!


Agreed, though ultimately we want to move to making mixing of ports &
pkgs idiot-proof - something I suspect we're in better shape to do with
pkgng. As a recently minted roadtester of pkgng and wanting to do the
same as Vitaly without setting up Poudriere, I had to reverse engineer
the ports tree svn revision to make sure I could mix and match from
pkgbeta and stuff I built locally via ports with WITH_NEW_XORG and
WITH_KMS. This becomes more annoying to manage going forward.

So far I'm enjoying my pkgng experience for the most part and wish to
thank all those involved in getting it to this stage.

Cheers,
Lawrence
___
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"

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

On Tue, Aug 21, 2012 at 03:26:43PM +0200, Jeremie Le Hen wrote:
> Hi Baptise,
> 
> On Mon, Aug 20, 2012 at 09:43:13PM +0200, Baptiste Daroussin wrote:
> > 
> > Since 1.0-rc6 release, everything looks ready for a final release of 1.0, 
> > I'll
> > give more details on the release commit bit :) this is planned for 30th 
> > august
> > 2012.
> > 
> > Current was supposed to switch to pkgng by default today, it has been 
> > delayed
> > until the nvidia-driver is fixed with pkgng. Thanksfully kwm@ and danfe@ has
> > been working on this, and the situation should be fixed pretty soon.
> > 
> > Please continue testing pkgng and reporting bugs, if you are new comers do 
> > not
> > hesitate to ask question about pkgng so that we can improve documentation:
> > 
> > The usual links about pkgng:
> >   - http://wiki.freebsd.org/pkgng
> >   - http://wiki.freebsd.org/PkgPrimer
> >   - https://github.com/pkgng/pkgng/blob/master/FAQ.md
> >   - http://people.freebsd.org/~bapt/pres-pkgng-bsdcan.pdf
> >   - http://www.youtube.com/watch?v=4Hxq7AHZ27I
> 
> First thank you and all who have worked to make this first release of
> pkgng.  This is a great milestone in FreeBSD history.
> 
> Supposedly, pkgng will stay opt-in for RELENG_9 and will be the default
> (opt-out?) on RELENG_10.  During the upgrade from the old branch to the
> new one, how do we ensure users will perform the required step
> (basically, run pkg2ng) to switch their pkg database to pkgng?  Will it
> be a note in src/UPDATING and as well in the release notes?
> 

Yes there will be a note in UPDATING, I'm also pondering modifying pkg_* tools
to that they show up an advetisement about pkg_install being deprecated.

I would also like to just remove pkg_* tools from RELENG_10 if that fits the
schedule.

regards,
Bapt


pgprE0wBGH62B.pgp
Description: PGP signature

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

2012-08-21 Thread Jeremie Le Hen

Hi Baptise,

On Mon, Aug 20, 2012 at 09:43:13PM +0200, Baptiste Daroussin wrote:
> 
> Since 1.0-rc6 release, everything looks ready for a final release of 1.0, I'll
> give more details on the release commit bit :) this is planned for 30th august
> 2012.
> 
> Current was supposed to switch to pkgng by default today, it has been delayed
> until the nvidia-driver is fixed with pkgng. Thanksfully kwm@ and danfe@ has
> been working on this, and the situation should be fixed pretty soon.
> 
> Please continue testing pkgng and reporting bugs, if you are new comers do not
> hesitate to ask question about pkgng so that we can improve documentation:
> 
> The usual links about pkgng:
>   - http://wiki.freebsd.org/pkgng
>   - http://wiki.freebsd.org/PkgPrimer
>   - https://github.com/pkgng/pkgng/blob/master/FAQ.md
>   - http://people.freebsd.org/~bapt/pres-pkgng-bsdcan.pdf
>   - http://www.youtube.com/watch?v=4Hxq7AHZ27I

First thank you and all who have worked to make this first release of
pkgng.  This is a great milestone in FreeBSD history.

Supposedly, pkgng will stay opt-in for RELENG_9 and will be the default
(opt-out?) on RELENG_10.  During the upgrade from the old branch to the
new one, how do we ensure users will perform the required step
(basically, run pkg2ng) to switch their pkg database to pkgng?  Will it
be a note in src/UPDATING and as well in the release notes?

-- 
Jeremie Le Hen

Scientists say the world is made up of Protons, Neutrons and Electrons.
They forgot to mention Morons.
___
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"

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

On Tue, Aug 21, 2012 at 12:37:26PM +0200, Olivier Smedts wrote:
> 2012/8/21 Baptiste Daroussin :
> > On Tue, Aug 21, 2012 at 12:09:46AM +0300, Vitaly Magerya wrote:
> >> What would be the best practice of mixing ports with packages?
> >
> > There is no best practice for that unfortunatly, (as actually) the best for 
> > you
> > is maybe to build your own pkgng repostories?
> > http://wiki.freebsd.org/PkgPrimer#Using_poudriere for example?
> 
> So, to make it really clear, one should *not* test, try or use pkgng
> if he wants to continue using ports without setting up a repository ?
> I did not find a big warning on the wiki.

to be clear you can continue to use your system with pkgng the same way you used
to use it before with pkg_install.

regards,
Bapt


pgpy8en8NIUJ7.pgp
Description: PGP signature

Re: pkgng, textproc/p5-XML-SAX-Expat: Syntax error: "{" unexpected (expecting "then")

2012-08-21 Thread Anton Shterenlikht

From utis...@gmail.com Tue Aug 21 12:10:39 2012
>
> Instead, as Baptiste advised me:
> cd /usr/ports/textproc/p5-XML-SAX-Expat
> make install FORCE_PKG_REGISTER=1
>
> In the case of pkgng the above command should do the right thing in 
this case
> (in-place upgrade).

Glad to see I remembered it correctly in my next message.

Chris

yes, this worked fine, thank you

Anton
___
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"

Re: pkgng, textproc/p5-XML-SAX-Expat: Syntax error: "{" unexpected (expecting "then")

On 21 August 2012 12:07, Andriy Gapon  wrote:
> on 21/08/2012 12:08 Chris Rees said the following:
>> On 21 August 2012 09:47, Anton Shterenlikht  wrote:
>>> # cd /usr/ports/textproc/p5-XML-SAX-Expat
>>> # make deinstall && make reinstall
>>> ===>  Deinstalling for textproc/p5-XML-SAX-Expat
>>> ===>   Deinstalling p5-XML-SAX-Expat-0.40
>>> The following packages will be deinstalled:
>>>
>>> p5-XML-SAX-Expat-0.40
>>>
>>> The deinstallation will free 22 kB
>>> Deinstalling p5-XML-SAX-Expat-0.40...p5-XML-SAX-Expat-0.40 is required by: 
>>> p5-XML-Simple-2.20 icon-naming-utils-0.8.90, deleting anyway
>>> Syntax error: "{" unexpected (expecting "then")
>>> pkg: DEINSTALL script failed
>>> *** [deinstall] Error code 3
>>>
>>> Stop in /usr/ports/textproc/p5-XML-SAX-Expat.
>>>
>>> # pkg -vvv
>>> version: 1.0-rc6
>>> abi: freebsd:10:ia64:64
>>> db dir: /var/db/pkg
>>> cache dir: /var/cache/pkg
>>> ports dir: /usr/ports
>>> Log into syslog: yes
>>> Assume always yes: no
>>> Handle rc scripts: no
>>> Track shlibs: no
>>> Automatic dependency tracking: no
>>> Custom keywords directory: none
>>> Developer mode: no
>>> Repository: ftp://ftp.freebsd.org/pub/pkgng
>>> #
>>
>> How long have you had this installed?
>>
>> Steve Wills [1] fixed the pkg-deinstall script yesterday, but
>> evidently you still have an older version.
>
> Right, but it's hard to upgrade to the new version without deinstalling the 
> old
> version, isn't it? :-)

D'oh, I forgot that make deinstall using pkg delete -f. Sorry.

>> If pkg delete hasn't removed it, try pkg delete -f, then reinstall.
>
> pkg delete -f won't help (as already shown in the original message).
>
> Instead, as Baptiste advised me:
> cd /usr/ports/textproc/p5-XML-SAX-Expat
> make install FORCE_PKG_REGISTER=1
>
> In the case of pkgng the above command should do the right thing in this case
> (in-place upgrade).

Glad to see I remembered it correctly in my next message.

Chris
___
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"

Re: pkgng, textproc/p5-XML-SAX-Expat: Syntax error: "{" unexpected (expecting "then")

On 21 August 2012 12:04, Anton Shterenlikht  wrote:
> From utis...@gmail.com Tue Aug 21 11:32:50 2012
>
> On 21 August 2012 09:47, Anton Shterenlikht  
> wrote:
> > # cd /usr/ports/textproc/p5-XML-SAX-Expat
> > # make deinstall && make reinstall
> > ===>  Deinstalling for textproc/p5-XML-SAX-Expat
> > ===>   Deinstalling p5-XML-SAX-Expat-0.40
> > The following packages will be deinstalled:
> >
> > p5-XML-SAX-Expat-0.40
> >
> > The deinstallation will free 22 kB
> > Deinstalling p5-XML-SAX-Expat-0.40...p5-XML-SAX-Expat-0.40 is 
> required by: p5-XML-Simple-2.20 icon-naming-utils-0.8.90, deleting anyway
> > Syntax error: "{" unexpected (expecting "then")
> > pkg: DEINSTALL script failed
> > *** [deinstall] Error code 3
> >
> > Stop in /usr/ports/textproc/p5-XML-SAX-Expat.
> >
> > # pkg -vvv
> > version: 1.0-rc6
> > abi: freebsd:10:ia64:64
> > db dir: /var/db/pkg
> > cache dir: /var/cache/pkg
> > ports dir: /usr/ports
> > Log into syslog: yes
> > Assume always yes: no
> > Handle rc scripts: no
> > Track shlibs: no
> > Automatic dependency tracking: no
> > Custom keywords directory: none
> > Developer mode: no
> > Repository: ftp://ftp.freebsd.org/pub/pkgng
> > #
>
> How long have you had this installed?
>
> Steve Wills [1] fixed the pkg-deinstall script yesterday, but
> evidently you still have an older version.
>
> If pkg delete hasn't removed it, try pkg delete -f, then reinstall.
>
> Chris
>
> [1] 
> http://www.freebsd.org/cgi/cvsweb.cgi/ports/textproc/p5-XML-SAX-Expat/pkg-deinstall
>
>
> # svn status -v /usr/ports/textproc/p5-XML-SAX-Expat/pkg-*inst*
> 302837   302833 swills   
> /usr/ports/textproc/p5-XML-SAX-Expat/pkg-deinstall
> 302837   302833 swills   
> /usr/ports/textproc/p5-XML-SAX-Expat/pkg-install
> # pkg delete -f p5-XML-SAX-Expat
> The following packages will be deinstalled:
>
> p5-XML-SAX-Expat-0.40
>
> The deinstallation will free 22 kB
>
> Proceed with deinstalling packages [y/N]: y
> Deinstalling p5-XML-SAX-Expat-0.40...p5-XML-SAX-Expat-0.40 is required by: 
> p5-XML-Simple-2.20 icon-naming-utils-0.8.90, deleting anyway
> Syntax error: "{" unexpected (expecting "then")
> pkg: DEINSTALL script failed
> #
>

Hm, bapt was talking about this earlier in IRC... I think if you make
-DFORCE_PKG_REGISTER -C /usr/ports/textproc/p5-XML-SAX-Expat install
clean you should be just fine.

Chris
___
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"

Re: pkgng, textproc/p5-XML-SAX-Expat: Syntax error: "{" unexpected (expecting "then")

2012-08-21 Thread Andriy Gapon

on 21/08/2012 12:08 Chris Rees said the following:
> On 21 August 2012 09:47, Anton Shterenlikht  wrote:
>> # cd /usr/ports/textproc/p5-XML-SAX-Expat
>> # make deinstall && make reinstall
>> ===>  Deinstalling for textproc/p5-XML-SAX-Expat
>> ===>   Deinstalling p5-XML-SAX-Expat-0.40
>> The following packages will be deinstalled:
>>
>> p5-XML-SAX-Expat-0.40
>>
>> The deinstallation will free 22 kB
>> Deinstalling p5-XML-SAX-Expat-0.40...p5-XML-SAX-Expat-0.40 is required by: 
>> p5-XML-Simple-2.20 icon-naming-utils-0.8.90, deleting anyway
>> Syntax error: "{" unexpected (expecting "then")
>> pkg: DEINSTALL script failed
>> *** [deinstall] Error code 3
>>
>> Stop in /usr/ports/textproc/p5-XML-SAX-Expat.
>>
>> # pkg -vvv
>> version: 1.0-rc6
>> abi: freebsd:10:ia64:64
>> db dir: /var/db/pkg
>> cache dir: /var/cache/pkg
>> ports dir: /usr/ports
>> Log into syslog: yes
>> Assume always yes: no
>> Handle rc scripts: no
>> Track shlibs: no
>> Automatic dependency tracking: no
>> Custom keywords directory: none
>> Developer mode: no
>> Repository: ftp://ftp.freebsd.org/pub/pkgng
>> #
> 
> How long have you had this installed?
> 
> Steve Wills [1] fixed the pkg-deinstall script yesterday, but
> evidently you still have an older version.

Right, but it's hard to upgrade to the new version without deinstalling the old
version, isn't it? :-)

> If pkg delete hasn't removed it, try pkg delete -f, then reinstall.

pkg delete -f won't help (as already shown in the original message).

Instead, as Baptiste advised me:
cd /usr/ports/textproc/p5-XML-SAX-Expat
make install FORCE_PKG_REGISTER=1

In the case of pkgng the above command should do the right thing in this case
(in-place upgrade).

> [1] 
> http://www.freebsd.org/cgi/cvsweb.cgi/ports/textproc/p5-XML-SAX-Expat/pkg-deinstall


-- 
Andriy Gapon
___
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"

Re: pkgng, textproc/p5-XML-SAX-Expat: Syntax error: "{" unexpected (expecting "then")

2012-08-21 Thread Anton Shterenlikht

From utis...@gmail.com Tue Aug 21 11:32:50 2012

On 21 August 2012 09:47, Anton Shterenlikht  wrote:
> # cd /usr/ports/textproc/p5-XML-SAX-Expat
> # make deinstall && make reinstall
> ===>  Deinstalling for textproc/p5-XML-SAX-Expat
> ===>   Deinstalling p5-XML-SAX-Expat-0.40
> The following packages will be deinstalled:
>
> p5-XML-SAX-Expat-0.40
>
> The deinstallation will free 22 kB
> Deinstalling p5-XML-SAX-Expat-0.40...p5-XML-SAX-Expat-0.40 is 
required by: p5-XML-Simple-2.20 icon-naming-utils-0.8.90, deleting anyway
> Syntax error: "{" unexpected (expecting "then")
> pkg: DEINSTALL script failed
> *** [deinstall] Error code 3
>
> Stop in /usr/ports/textproc/p5-XML-SAX-Expat.
>
> # pkg -vvv
> version: 1.0-rc6
> abi: freebsd:10:ia64:64
> db dir: /var/db/pkg
> cache dir: /var/cache/pkg
> ports dir: /usr/ports
> Log into syslog: yes
> Assume always yes: no
> Handle rc scripts: no
> Track shlibs: no
> Automatic dependency tracking: no
> Custom keywords directory: none
> Developer mode: no
> Repository: ftp://ftp.freebsd.org/pub/pkgng
> #

How long have you had this installed?

Steve Wills [1] fixed the pkg-deinstall script yesterday, but
evidently you still have an older version.

If pkg delete hasn't removed it, try pkg delete -f, then reinstall.

Chris

[1] 
http://www.freebsd.org/cgi/cvsweb.cgi/ports/textproc/p5-XML-SAX-Expat/pkg-deinstall


# svn status -v /usr/ports/textproc/p5-XML-SAX-Expat/pkg-*inst*
302837   302833 swills   
/usr/ports/textproc/p5-XML-SAX-Expat/pkg-deinstall
302837   302833 swills   
/usr/ports/textproc/p5-XML-SAX-Expat/pkg-install
# pkg delete -f p5-XML-SAX-Expat
The following packages will be deinstalled:

p5-XML-SAX-Expat-0.40

The deinstallation will free 22 kB

Proceed with deinstalling packages [y/N]: y
Deinstalling p5-XML-SAX-Expat-0.40...p5-XML-SAX-Expat-0.40 is required by: 
p5-XML-Simple-2.20 icon-naming-utils-0.8.90, deleting anyway
Syntax error: "{" unexpected (expecting "then")
pkg: DEINSTALL script failed
# 

Thanks

Anton
___
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"

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

On 21 August 2012 11:37, Olivier Smedts  wrote:
> 2012/8/21 Baptiste Daroussin :
>> On Tue, Aug 21, 2012 at 12:09:46AM +0300, Vitaly Magerya wrote:
>>> What would be the best practice of mixing ports with packages?
>>
>> There is no best practice for that unfortunatly, (as actually) the best for 
>> you
>> is maybe to build your own pkgng repostories?
>> http://wiki.freebsd.org/PkgPrimer#Using_poudriere for example?
>
> So, to make it really clear, one should *not* test, try or use pkgng
> if he wants to continue using ports without setting up a repository ?
> I did not find a big warning on the wiki.

You can of course use pkgng with ports-- nothing has changed in that
respect; putting WITH_PKGNG=yes into /etc/make.conf makes the ports
tree work just fine.

It has never been recommended to use packages and ports together.

Chris
___
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"

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule

2012-08-21 Thread Olivier Smedts

2012/8/21 Baptiste Daroussin :
> On Tue, Aug 21, 2012 at 12:09:46AM +0300, Vitaly Magerya wrote:
>> What would be the best practice of mixing ports with packages?
>
> There is no best practice for that unfortunatly, (as actually) the best for 
> you
> is maybe to build your own pkgng repostories?
> http://wiki.freebsd.org/PkgPrimer#Using_poudriere for example?

So, to make it really clear, one should *not* test, try or use pkgng
if he wants to continue using ports without setting up a repository ?
I did not find a big warning on the wiki.

-- 
Olivier Smedts _
ASCII ribbon campaign ( )
e-mail: oliv...@gid0.org- against HTML email & vCards  X
www: http://www.gid0.org- against proprietary attachments / \

  "Il y a seulement 10 sortes de gens dans le monde :
  ceux qui comprennent le binaire,
  et ceux qui ne le comprennent pas."
___
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"

Re: Attempting to fetch pkgconf-0.8.7.tar.bz2, Couldn't fetch it

2012-08-21 Thread Enrique Ayesta Perojo

El Martes, 21 de Agosto de 2012 11:55, Baptiste Daroussin escribió:
>
> I just added a mirror to solve the problem.
>
> regards,
> Bapt

Thanks, it works now
___
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"

Re: Attempting to fetch pkgconf-0.8.7.tar.bz2, Couldn't fetch it

On Tue, Aug 21, 2012 at 10:23:11AM +0200, Enrique Ayesta Perojo wrote:
> El Martes, 21 de Agosto de 2012 10:03, Leslie Jensen escribió:
> > Hi
> >
> > Is anyone else seeing this problem?
> >
> > /Leslie
> >
> > => Attempting to fetch
> > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/pkgconf-0.8.7.tar.bz2
> > fetch:
> > ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/pkgconf-0.8.7.tar.bz2:
> > File unavailable (e.g., file not found, no access)
> > => Couldn't fetch it - please try to retrieve this
> > => port manually into /usr/ports/distfiles// and try again.
> > *** Error code 1
> >
> 
> 
> Hi,
> 
> Yes, i have the same problem
> ___
> 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"

I just added a mirror to solve the problem.

regards,
Bapt


pgpv4yrVfiLav.pgp
Description: PGP signature

Re: pkg(ng)/portupgrade-devel: does not respect setting of USE_GCC= 4.6+

2012-08-21 Thread Andrew W. Nosenko

On Mon, Aug 20, 2012 at 10:39 PM, O. Hartmann
 wrote:
> I'm pretty sure, that the last time I updated port math/fftw3 I wanted
> option OpenMP enabled so I declared "USE_GCC=4.6+" in make.conf. Later,
> also working!, I excluded all these user definitions into an external
> file called ports.conf located in /usr/local/etc (I like this clean
> separation of OS and user messes ;-) ). Suddenly it doesn't work
> anymore. There were changes in several Mk files located in /usr/ports/Mk.

Beware!  Even if you will be able to force gcc-4.6 to be used and thus
obtain OpenMP-3.1 at the compilation stage, the libgomp.so.1, which
will be used at run-time, will be OpenMP-3.0 from the base gcc-4.2
(/usr/lib/libgomp.so.1 on my FreeBSD-8.0 system).  Also, as a bonus,
you may be exposed to ancient bugs from the gcc-4.2 openmp
implementation.  For me, personally, it is memory leak as described in
http://gcc.gnu.org/ml/gcc/2009-05/msg00427.html
Fixed in gcc-4.3, but gcc-4.3 never was nor will be in base.

Thus...  For obtain the proper openmp you will either limit yourself
to openmp-3.0 from gcc-4.2 and workaround known bugs, or make a black
magic dance for override and "unsteal" the libgomp (e.g. using
libmap.conf) and have maintenance problem every time when gcc version
changes (and, therefore, changes the directory name, where gcc
libraries live).

-- 
Andrew W. Nosenko 
___
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"

raptor: should there be a note in UPDATING?

2012-08-21 Thread Robert Backhaus

I just had a problem building liblrdf. The cause was raptor-1 was
still installed. Checking UPDATING shows nothing that mentions raptor
after the KDE update last November.
Does there need to a note in UPDATING to uninstall raptor?
___
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"

Re: pkgng, textproc/p5-XML-SAX-Expat: Syntax error: "{" unexpected (expecting "then")

On 21 August 2012 09:47, Anton Shterenlikht  wrote:
> # cd /usr/ports/textproc/p5-XML-SAX-Expat
> # make deinstall && make reinstall
> ===>  Deinstalling for textproc/p5-XML-SAX-Expat
> ===>   Deinstalling p5-XML-SAX-Expat-0.40
> The following packages will be deinstalled:
>
> p5-XML-SAX-Expat-0.40
>
> The deinstallation will free 22 kB
> Deinstalling p5-XML-SAX-Expat-0.40...p5-XML-SAX-Expat-0.40 is required by: 
> p5-XML-Simple-2.20 icon-naming-utils-0.8.90, deleting anyway
> Syntax error: "{" unexpected (expecting "then")
> pkg: DEINSTALL script failed
> *** [deinstall] Error code 3
>
> Stop in /usr/ports/textproc/p5-XML-SAX-Expat.
>
> # pkg -vvv
> version: 1.0-rc6
> abi: freebsd:10:ia64:64
> db dir: /var/db/pkg
> cache dir: /var/cache/pkg
> ports dir: /usr/ports
> Log into syslog: yes
> Assume always yes: no
> Handle rc scripts: no
> Track shlibs: no
> Automatic dependency tracking: no
> Custom keywords directory: none
> Developer mode: no
> Repository: ftp://ftp.freebsd.org/pub/pkgng
> #

How long have you had this installed?

Steve Wills [1] fixed the pkg-deinstall script yesterday, but
evidently you still have an older version.

If pkg delete hasn't removed it, try pkg delete -f, then reinstall.

Chris

[1] 
http://www.freebsd.org/cgi/cvsweb.cgi/ports/textproc/p5-XML-SAX-Expat/pkg-deinstall
___
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"

Happy Birthday FreeBSD ports

2012-08-21 Thread Beat Gaetzi

Hi,

Today, 18 years ago the first version of Mk/bsd.port.mk was committed
to CVS. From the CVS log:

# cvs log -r1.1 Mk/bsd.port.mk
Working file: Mk/bsd.port.mk
head: 1.738
[...]
description:

revision 1.1
date: 1994/08/21 13:12:57;  author: jkh;  state: Exp;
Commit my new ports make macros.  Still not 100% complete yet by any means
but fairly usable at this stage.
Submitted by:   jkh

A couple of minutes later the first ports were committed:
editors/emacs
editors/jove
shells/bash

>From the CVS log:

# cvs log -r1.1.1.1 editors/jove/Makefile
Working file: editors/jove/Makefile
head: 1.23
[...]
description:

revision 1.1.1.1
date: 1994/08/21 13:19:28;  author: jkh;  state: Exp;  lines: +0 -0
The start of the 2.0 ports collection.  No sup repository yet, but I'll
make one when I wake up again.. :)
Submitted by:   jkh

This means that (at least in some countries) the ports tree is grown-up
now.

Happy Birthday!
Beat (on behalf of portmgr@)
___
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"

pkgng, textproc/p5-XML-SAX-Expat: Syntax error: "{" unexpected (expecting "then")

2012-08-21 Thread Anton Shterenlikht

# cd /usr/ports/textproc/p5-XML-SAX-Expat
# make deinstall && make reinstall
===>  Deinstalling for textproc/p5-XML-SAX-Expat
===>   Deinstalling p5-XML-SAX-Expat-0.40
The following packages will be deinstalled:

p5-XML-SAX-Expat-0.40

The deinstallation will free 22 kB
Deinstalling p5-XML-SAX-Expat-0.40...p5-XML-SAX-Expat-0.40 is required by: 
p5-XML-Simple-2.20 icon-naming-utils-0.8.90, deleting anyway
Syntax error: "{" unexpected (expecting "then")
pkg: DEINSTALL script failed
*** [deinstall] Error code 3

Stop in /usr/ports/textproc/p5-XML-SAX-Expat.

# pkg -vvv
version: 1.0-rc6
abi: freebsd:10:ia64:64
db dir: /var/db/pkg
cache dir: /var/cache/pkg
ports dir: /usr/ports
Log into syslog: yes
Assume always yes: no
Handle rc scripts: no
Track shlibs: no
Automatic dependency tracking: no
Custom keywords directory: none
Developer mode: no
Repository: ftp://ftp.freebsd.org/pub/pkgng
# 

# uname -a
FreeBSD mech-cluster241.men.bris.ac.uk 10.0-CURRENT FreeBSD 10.0-CURRENT #6 
r237134: Mon Jun 18 09:02:17 BST 2012 
r...@mech-cluster241.men.bris.ac.uk:/usr/obj/usr/src/sys/TZAV  ia64
#
___
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"

FreeBSD unmaintained ports which are currently scheduled for deletion

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically schedule removal of ports
that have been judged to have outlived their usefulness.  Often,
this is due to a better alternative having become available and/or
the cessation of development on the existing port.  In some cases,
ports are marked for removal because they fail to build and install
correctly from their sources, or otherwise fail in operation.

The ports, and the reason and date that they have been scheduled
for removal, are listed below.  If no one has stepped forward before
that time to propose a way to fix the problems (such as via a PR),
the ports will be deleted.



portname:   archivers/bsdar
description:BSD-licensed replacement of the ar utility
maintainer: po...@freebsd.org
status: IGNORE
deprecated because: part of the base system
expiration date:2013-02-28
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=bsdar


portname:   audio/linux-alsa-lib
description:The Advanced Linux Sound Architecture libraries
maintainer: po...@freebsd.org
deprecated because: 
expiration date:2013-02-28
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-alsa-lib


portname:   audio/linux-arts
description:Audio system for the KDE integrated X11 desktop (Linux
version)
maintainer: po...@freebsd.org
deprecated because: 
expiration date:2013-02-28
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-arts


portname:   audio/linux-freealut
description:A free implementation of OpenAL's ALUT standard (Linux
version)
maintainer: po...@freebsd.org
deprecated because: 
expiration date:2013-02-28
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-freealut


portname:   audio/linux-libmad
description:Libmad library (part of MAD project)
maintainer: po...@freebsd.org
deprecated because: 
expiration date:2013-02-28
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-libmad


portname:   audio/linux-libogg
description:Ogg bitstream library (Linux version)
maintainer: po...@freebsd.org
deprecated because: 
expiration date:2013-02-28
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-libogg


portname:   audio/linux-libvorbis
description:Audio compression codec library (Linux version)
maintainer: po...@freebsd.org
deprecated because: 
expiration date:2013-02-28
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-libvorbis


portname:   audio/linux-openal
description:A 3D positional spatialized sound library (Linux
version)
maintainer: po...@freebsd.org
deprecated because: 
expiration date:2013-02-28
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-openal


portname:   databases/libudbc
description:Openlink UDBC SDK
maintainer: po...@freebsd.org
deprecated because: Does not fetch and no vendor support anymore
expiration date:2012-08-12
build errors:
http://pointyhat.FreeBSD.org/errorlogs/i386-errorlogs/e.7.20120731073932/libudbc-4.1.log
 (_Aug__2_00:21:36_UTC_2012)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=libudbc


portname:   devel/libgetline
description:A small, portable, and easy to use command line
library
maintainer: po...@freebsd.org
deprecated because: Upstream disapear and distfile is no more available
expiration date:2013-02-28
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=libgetline


portname:   graphics/linux-cairo
description:Linux cairo binary
maintainer: po...@freebsd.org
deprecated because: 
expiration date:2013-02-28
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-cairo


portname:   graphics/linux-gdk-pixbuf
description:Linux version of the graphic library for GTK+
maintainer: po...@freebsd.org
deprecated because: 
expiration date:2013-02-28
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-gdk-pixbuf


portname:   java/sun-wtk
description:Sun J2ME Wireless

FreeBSD ports which are currently marked forbidden

As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles.  Often,
these ports are so marked due to security concerns, such as known
exploits.

An overview of each port, including errors seen on the build farm,
is included below.

portname:   graphics/linux-tiff
forbidden because:  Vulnerable since 2004-10-13,

http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff


portname:   security/sudosh3
forbidden because:  Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo
(55903), replay() function buffer overflow.
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3


portname:   www/linux-f10-flashplugin10
forbidden because:  insecure version - use flashplugin11
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-f10-flashplugin10


portname:   x11-toolkits/linux-pango
forbidden because:  Vulnerable since 2009-05-13,

http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango
___
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"

FreeBSD ports which are currently marked broken

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles.  In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments.  The most common problem is that recent versions
of -CURRENT include gcc4.2, which is much stricter than older versions.
The next most common problem is that compiles succeed on the i386
architecture (e.g. the common Intel PC), but fail on one or more
of the other architectures due to assumptions about things such as
size of various types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments.  The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm.  Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below.  In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type.  (By 'build environment' here we
mean 'combination of 7.x/8.x/9.x/-current with target architecture'.)

(Note: the dates are included to help you to gauge whether or not
the error still applies to the latest version.  The program
that generates this report is not yet able to determine this
automatically.)

portname:   accessibility/yasr
broken because: fails to build with new utmpx
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=accessibility&portname=yasr


portname:   audio/gdam
broken because: does not build
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.8.20120820105642/gdam-0.942_9.log
 (_Aug_21_02:41:04_UTC_2012)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=gdam


portname:   audio/hydrogen
broken because: does not install
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=hydrogen


portname:   audio/teamspeak_client
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=teamspeak_client


portname:   benchmarks/polygraph31
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=benchmarks&portname=polygraph31


portname:   cad/feappv
broken because: size mismatch
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20120810200026/feappv-3.1.log
 (_Aug__6_16:25:29_UTC_2012)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=feappv


portname:   cad/meshlab
broken because: does not build
build errors:
http://pointyhat.FreeBSD.org/errorlogs/i386-errorlogs/e.8.20120730062936/meshlab-1.3.0.log
 (_Jul_31_05:31:08_UTC_2012)
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.10.20120628171716/meshlab-1.2.3_2.log
 (_Jul_16_09:33:26_UTC_2012)
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=meshlab


portname:   cad/salome-gui
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=salome-gui


portname:   chinese/big5con
broken because: fails to build with new utmpx
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=big5con


portname:   chinese/cxterm
broken because: fails to build with new utmpx
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=cxterm


portname:   chinese/hztty
broken because: fails to build with new utmpx
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=hztty


portname:   comms/hso-kmod
broken because: does not build with USB2, please try comms/uhso-kmod
instead
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=hso-kmod


portname:   comms/ib-kmod
broken because: does not build
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=ib-kmod


portname:   comms/uticom
broken because: does not compile
build errors:   none.
overview:   
http://portsmon.FreeBSD.org/portoverview.py?category=comms&portname=uticom


portname:   databases/adstudio
broken because:

FreeBSD unmaintained ports which are currently marked broken

As part of an ongoing effort to reduce the number of problems in
the FreeBSD ports system, we periodically notify users of ports
that are marked as "broken" in their Makefiles. In many cases
these ports are failing to compile on some subset of the FreeBSD
build environments. The most common problem is that recent versions
of -CURRENT include gcc4.2, which is much stricter than older versions.
The next most common problem is that compiles succeed on the i386
architecture (e.g. the common Intel PC), but fail on one or more
of the other architectures due to assumptions about things such as
size of various types, byte-alignment issues, and so forth.

In occasional cases we see that the same port may have different
errors in different build environments. The script that runs on the
build cluster uses heuristics to try to 'guess' the error type to
help you isolate problems, but it is only a rough guide.

One more note: on occasion, there are transient build errors seen
on the build farm. Unfortunately, there is not yet any way for this
algorithm to tell the difference (humans are much, much better at
this kind of thing.)

The errors are listed below. In the case where the same problem
exists on more than one build environment, the URL points to the
latest errorlog for that type. (By 'build environment' here we
mean 'combination of 7.x/8.x/9.x/-current with target architecture'.)

(Note: the dates are included to help you to gauge whether or not
the error still applies to the latest version. The program
that generates this report is not yet able to determine this
automatically.)

portname: audio/teamspeak_client
broken because: does not build
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=teamspeak_client

portname: cad/feappv
broken because: size mismatch
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.7.20120810200026/feappv-3.1.log
(_Aug__6_16:25:29_UTC_2012)
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=cad&portname=feappv

portname: chinese/big5con
broken because: fails to build with new utmpx
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=big5con

portname: chinese/hztty
broken because: fails to build with new utmpx
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=hztty

portname: databases/adstudio
broken because: incomplete plist
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=adstudio

portname: databases/grass
broken because: does not build
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=grass

portname: databases/msql
broken because: Broken on FreeBSD 9+
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=msql

portname: databases/xapian-bindings10
broken because: does not compile
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=xapian-bindings10

portname: deskutils/simpleagenda
broken because: does not build
build errors:
http://pointyhat.FreeBSD.org/errorlogs/amd64-errorlogs/e.9.20120802074109/simpleagenda-0.42.log
(_Aug__3_22:06:24_UTC_2012)
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=deskutils&portname=simpleagenda

portname: devel/dsss
broken because: does not build
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=dsss

portname: devel/gauche-gaunit
broken because: does not package
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=gauche-gaunit

portname: devel/gcvs
broken because: does not compile
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=gcvs

portname: devel/linux-js
broken because: does not build
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linux-js

portname: devel/linuxthreads
broken because: does not build
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linuxthreads

portname: devel/lua-posix
broken because: does not build
build errors: none.
overview:
http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=lua-posix

portname: devel/lua50-posix
broken because: does not build
build errors:
http://pointyhat.FreeBSD.org/errorlogs/

Re: Attempting to fetch pkgconf-0.8.7.tar.bz2, Couldn't fetch it

2012-08-21 Thread Enrique Ayesta Perojo

El Martes, 21 de Agosto de 2012 10:03, Leslie Jensen escribió:
> Hi
>
> Is anyone else seeing this problem?
>
> /Leslie
>
> => Attempting to fetch
> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/pkgconf-0.8.7.tar.bz2
> fetch:
> ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/pkgconf-0.8.7.tar.bz2:
> File unavailable (e.g., file not found, no access)
> => Couldn't fetch it - please try to retrieve this
> => port manually into /usr/ports/distfiles// and try again.
> *** Error code 1
>


Hi,

Yes, i have the same problem
___
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"

Attempting to fetch pkgconf-0.8.7.tar.bz2, Couldn't fetch it

2012-08-21 Thread Leslie Jensen



Hi


Is anyone else seeing this problem?

/Leslie



=> Attempting to fetch 
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/pkgconf-0.8.7.tar.bz2
fetch: 
ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/pkgconf-0.8.7.tar.bz2: 
File unavailable (e.g., file not found, no access)

=> Couldn't fetch it - please try to retrieve this
=> port manually into /usr/ports/distfiles// and try again.
*** Error code 1

___
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"

Re: pkgng 1.0 release schedule, and HEAD switch to pkgng by default schedule