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 pra
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 fe
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
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 probl
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 probl
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, inclu
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 th
# 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-
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
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-Ex
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@freebs
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 l
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
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-port
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?
>
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
>
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
> ===> Deinstall
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 followi
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
> > ===> Dei
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
>>> ===
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 ca
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 actua
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
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
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
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:
> B
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
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 de
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
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
> pk
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
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 mis
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
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?
>
> ...
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
befor
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 pk
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 i
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 abl
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 schedul
On FreeBSD 9.0 Release I got:
portmaster -a
===>>> Gathering distinfo list for installed ports
===>>> Starting check of installed ports for available updates
===>>> Launching child to update liblrdf-0.4.0_2 to liblrdf-0.5.0
===>>> All >> liblrdf-0.4.0_2 (1/1)
===>>> Currently installed version:
On Tue, Aug 21, 2012 at 1:15 PM, Doug Barton wrote:
> 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
Robert Backhaus writes:
> 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?
It seems more appropriate to fix
ajtiM writes:
> ===>>> make failed for textproc/liblrdf
> ===>>> Aborting update
>
> ===>>> Update for textproc/liblrdf failed
> ===>>> Aborting update
Please see the other thread about the same issue.
___
freebsd-ports@freebsd.org mailing list
http:/
Raphael Kubo da Costa writes:
> Someone (TM) should check whether the first include is really necessary,
> or if the code can't include , or if
> -I/usr/local/include/raptor2 can't be passed before
> -I/usr/local/include.
Everything built fine without the {CPP,LD}FLAGS additions here. I'm
tempte
On Tue, 21 Aug 2012, Doug Barton wrote:
I don't think we have ever done a complete replacement of major
infrastructure in one release.
You mean like sysinstall can be used as an installer on 9 that would
do something meaningful with the current infrastructure we provide?
--
Bjoern A. Zeeb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Everyone,
Thanks for all of this info. regarding the port changes that should
be done. I haven't played with the port system in a while so I'm
definitely a bit rusty and I'm sure there have been many changes
(Hence the Apache 2.0 bit... :o!
Hi,
I did a quick hack to make porttools work with svn. It's far from perfect, but
it makes "port submit" work for me. It's available here:
http://meatwad.mouf.net/~steve/porttools_svn.diff
and attached. If anyone wants to finish it up, that'd be cool.
Steve
--- /usr/local/share/porttools/cmd
On Tue, Aug 21, 2012 at 10:35 PM, Steve Wills wrote:
> Hi,
>
> I did a quick hack to make porttools work with svn. It's far from perfect,
> but it makes "port submit" work for me. It's available here:
>
> http://meatwad.mouf.net/~steve/porttools_svn.diff
It looks like the diff might be reversed
Yes, sorry, see attached. URL updated...
Steve
On Aug 21, 2012, at 10:41 PM, Steven Kreuzer wrote:
> On Tue, Aug 21, 2012 at 10:35 PM, Steve Wills wrote:
>> Hi,
>>
>> I did a quick hack to make porttools work with svn. It's far from perfect,
>> but it makes "port submit" work for me. It's ava
Am 22.08.2012 04:49, schrieb Steve Wills:
> Yes, sorry, see attached. URL updated...
>
>>> http://meatwad.mouf.net/~steve/porttools_svn.diff
The patch at the online URL is correct now, the attached diff was still
reversed.
Steve, if any issues with the psvn script surface, do not hesitate to
Cc:
On Tue, Aug 21, 2012 at 02:43:13PM -0700, Garrett Cooper wrote:
>
> What Doug mentioned (and I don't think was really considered, but
> is valid) would break people that use pkg_* outside of ports. I know
> of at least two instances where this would be the case (one case that
> uses pkg_* dire
51 matches
Mail list logo
