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 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
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
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
On Fri, Aug 07, 2009 at 08:17:20AM +0800, Erich Dollansky wrote:
> Hi,
>
> On 06 August 2009 pm 19:10:07 Lars Eighner wrote:
> >
> > Would these things build if I deleted all 1619 installed
> > packages and started from scratch, or are the circular gotchas
> > built-in with python and qt?
>
> do
On Thursday 06 August 2009 19:29:24 Lars Eighner wrote:
> On Thu, 6 Aug 2009, Mel Flynn wrote:
> > On Thursday 06 August 2009 17:38:40 Lars Eighner wrote:
> >> It's hard to resist the sales pitch (really, USB will work again on
> >> 8.0, we promise! [but we are going to trash your modem driver]) --
Lars Eighner wrote:
> Believe me, if I can get back to my printer, camera, and mp3 player
> all working (which last occurred about 6.2 or so) I'll never upgrade
> again. Of course it is kind of lonely when your release is orphaned,
> which happens in the blink of an eye, but if the kernel support
Hi,
On 07 August 2009 am 11:29:24 Lars Eighner wrote:
> On Thu, 6 Aug 2009, Mel Flynn wrote:
> > On Thursday 06 August 2009 17:38:40 Lars Eighner wrote:
>
> Done, months ago with all the core dump stuff. Still open.
> Umass still crashes the system if I plug the camera or the mp3
> player in. (
On Thu, 6 Aug 2009, Mel Flynn wrote:
On Thursday 06 August 2009 17:38:40 Lars Eighner wrote:
It's hard to resist the sales pitch (really, USB will work again on
8.0, we promise! [but we are going to trash your modem driver]) ---
sooner or later one has to wise up.
If you actually know how re
On Thursday 06 August 2009 17:38:40 Lars Eighner wrote:
> It's hard to resist the sales pitch (really, USB will work again on
> 8.0, we promise! [but we are going to trash your modem driver]) ---
> sooner or later one has to wise up.
If you actually know how responsive in particular hps@ is at pe
Hi,
On 07 August 2009 am 10:14:25 b. f. wrote:
> On 8/7/09, Erich Dollansky wrote:
> > On 07 August 2009 am 08:44:44 b. f. wrote:
> >> Erich Dollansky wrote:
> >> >If this would be synchronised with the main FreeBSD
> >> > releases, it would have a minor effect on users.
> >>
> >> But please don
Hi,
On 07 August 2009 am 09:29:59 Lars Eighner wrote:
> On Fri, 7 Aug 2009, Erich Dollansky wrote:
> > On 06 August 2009 pm 19:10:07 Lars Eighner wrote:
> >
> > do not even ask this question if you have a working system.
> >
> > I realised this problem by luck when I tried to update a
> > single p
On 8/7/09, Erich Dollansky wrote:
> Hi,
>
> On 07 August 2009 am 08:44:44 b. f. wrote:
>> Erich Dollansky wrote:
>> >I think that you hit the weakest point of FreeBSD. When a
>> > version number of a base port changes, hundreds or even
>> > thousands of ports have to be recompiled. It is basically
On Fri, 7 Aug 2009, b. f. wrote:
If this would be synchronised with the main FreeBSD releases, it
would have a minor effect on users.
No one is _forcing_ you to update anything, or even to use ports at
all.
Believe me, if I can get back to my printer, camera, and mp3 player
all working (whic
On Fri, 7 Aug 2009, Erich Dollansky wrote:
Hi,
On 06 August 2009 pm 19:10:07 Lars Eighner wrote:
Would these things build if I deleted all 1619 installed
packages and started from scratch, or are the circular gotchas
built-in with python and qt?
do not even ask this question if you have a w
Hi,
On 07 August 2009 am 08:44:44 b. f. wrote:
> Erich Dollansky wrote:
> >I think that you hit the weakest point of FreeBSD. When a
> > version number of a base port changes, hundreds or even
> > thousands of ports have to be recompiled. It is basically the
> > same effect as when the major versi
Erich Dollansky wrote:
>I think that you hit the weakest point of FreeBSD. When a version
>number of a base port changes, hundreds or even thousands of
>ports have to be recompiled. It is basically the same effect as
>when the major version number of FreeBSD changes.
The same is true of almost any
That is a very nice idea, I am sure that with a little tweaking it would turn
out just fine.
Another nice aspect or solve for this would be getting something going like
symbol versioning in the libs by means of the developer that supports 2 or so
version's prior to the current lib in order to e
Hi,
On 06 August 2009 pm 19:10:07 Lars Eighner wrote:
>
> Would these things build if I deleted all 1619 installed
> packages and started from scratch, or are the circular gotchas
> built-in with python and qt?
do not even ask this question if you have a working system.
I realised this problem b
The meaning of NODE_VERSION and the flag is to describe dependencies more
detailed,
to make it possible to do automated upgrade, instead of bump PORTREVISION by
man.
An important thing, NODE_VERSION and the flag could be backward compatible,
for port/package don't have NODE_VERSION, it's just 0.
t
I believe unless I misunderstand what you are meaning, is the same thing that
PORTREVISION is meant for doing. If the maintainer like what has just recently
happened for jpeg bumps the PORTREVISION up one for every port that depends on
jpeg then any upgrade utilities see that port as a new vers
Hi,
> [2009/8/6 Kenneth Dombrowski ]
> An attempt to package py-dbutils looks like this:
>
> r...@db2 ports $ portupgrade -pf databases/py-dbutils
> Creating package /usr/ports/packages/All/py25-dbutils-1.0.tbz
> Registering depends: python25-2.5.4_2.
> Creating bzip'd tar ball in '/usr/ports/pack
> Hi all,
>
> I have a cluster of webservers running apache22 + python25 + webware
> for python 0.9.3. I am building a few new servers to add to the
> cluster & took the opportunity to update ports-all for the first time
> in awhile. I have one package server, where everything is built from
> sou
Doug Barton wrote:
> All the other qt4 stuff updated just fine, this one doesn't (and I
> already disabled make-jobs).
Well I'm a bit embarrassed. :-/ I just re-read the UPDATING entry on
qt4 stuff and it turns out that this issue is mentioned. Deleting the
port first and then installing it works
Lars Eighner wrote:
> On Wed, 5 Aug 2009, Doug Barton wrote:
>
>> Naram Qashat wrote:
>>
>>> Actually, I had this problem as well, I found the solution (after a bit
>>> of Googling), is to deinstall devel/dbus-qt4 and then install it again.
>>> Apparently the update conflicts with the older versio
Matthias Andree wrote:
> Am 06.08.2009, 05:38 Uhr, schrieb Doug Barton :
>
>
>> I have considered changing the order of how portmaster does things from:
>>
>> build
>> backup package (unless -B)
>> deinstall
>> install
>>
>> to:
>> backup package
>> deinstall
>> build
>> install
>>
>> That is und
Kent Stewart wrote:
> I had the same problem. It was fixed in a later update. You need to cvsup
> again or what ever you use.
I already have the latest version.
> You may hit problem with phonon, which the current UPDATING tells you to
> delete. Using portupgrade, kdepim was updated after kde
On Thursday 06 August 2009 08:52:27 am Doug Barton wrote:
> All the other qt4 stuff updated just fine, this one doesn't (and I
> already disabled make-jobs).
>
>
> Doug
>
> c++ -c -pipe -g -g -O2 -Wall -W -D_LARGEFILE64_SOURCE
> -D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_SCRIPT_LIB -DQT_XML_LIB
> -DQT_
All the other qt4 stuff updated just fine, this one doesn't (and I
already disabled make-jobs).
Doug
c++ -c -pipe -g -g -O2 -Wall -W -D_LARGEFILE64_SOURCE
-D_LARGEFILE_SOURCE -DQT_NO_DEBUG -DQT_SCRIPT_LIB -DQT_XML_LIB
-DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED
-I/usr/local/share/qt4
khsing wrote:
> I have found the reason. because libtool15 have been mv to libtool22.
>
> so upgrade libtool from 15 to 22 will resolve this problem.
>
> portmaster -Btuw libtool
Please check ports/UPDATING for the correct procedure. Of the flags
you suggested, -t and -u are meaningless in this
Hi all,
I have a cluster of webservers running apache22 + python25 + webware
for python 0.9.3. I am building a few new servers to add to the
cluster & took the opportunity to update ports-all for the first time
in awhile. I have one package server, where everything is built from
source using `po
I'm having a problem building rails with ruby 1.9. It seems to depend on
'rubygem-rake' but that is apparently to be included with ruby 1.9. See
below.
Cheers,
Stef
RAILS INSTALL OUTPUT
/usr/ports/www/rubygem-rails # make install
===> Installing for rubygem-rails-2.3.3
===> rubygem-rails-2.
>but x11-toolkits/py-gtk2 will not build with py26-cairo, but insists on
> py25-cairo which will not build with or without python26
>I realize this stuff is put together by object-oriented people who aren't
>really used to the expectation that stuff will, you know, actually work.
You're chasing
2009/8/6 Mel Flynn :
> On Wednesday 05 August 2009 20:08:55 Doug Barton wrote:
>> Ok, so now I'm up to the point where starting contool give me this:
>>
>> contool
>> Assertion failed: (ret != inval_id), function _XAllocID, file
>> xcb_io.c, line 378.
>> Abort trap: 6 (core dumped)
>
> You get a be
Hi,
I have tried to install bsd-airtools from your ports collection, but as
you can see there appears to be a problem. Any suggestions?
[jig...@mageddo]$ cd /usr/ports/net-mgmt/bsd-airtools
[jig...@mageddo]$ sudo make install clean
===> bsd-airtools-0.3 broken by removal of wicontrol ioctls
On Thu, 06 Aug 2009 01:35:32 -0500, khsing wrote:
I have found the reason. because libtool15 have been mv to libtool22.
It is documented in /usr/ports/UPDATING.
so upgrade libtool from 15 to 22 will resolve this problem.
portmaster -Btuw libtool
On Thu, Aug 6, 2009 at 12:36 PM, 葉佳威 Jiawei
Okay py25-cairo will not build with python26
But with python26 it won't build either.
py26-cairo will build with python26 and replaces py25-cairo
but x11-toolkits/py-gtk2 will not build with py26-cairo, but insists on
py25-cairo which will not build with or without python26
I realize this stu
Le Wed, 05 Aug 2009 18:50:25 +0200,
t_ziel a écrit :
> The latest development snapshot is dated: 2009-01-13 so it's not too
> old, nor dead.
> http://gforge.inria.fr/frs/?group_id=184
Se 2 is mostly dead:
http://n2.nabble.com/Status-of-SmartEiffel-(alive-or-dead)-td3085602.html
> If SmartEiffe
On Wed, 5 Aug 2009, Florent Thoumie wrote:
On Tue, Aug 4, 2009 at 9:48 PM, Lars Eighner wrote:
What does py25 mean?
I can't seem to upgrade about 40 ports (the old versions of which now seem
to be broken) evidently because the build of
py25-gtk-2.13.1 fails with the message
py25-cairo-1.8
Am 06.08.2009, 05:38 Uhr, schrieb Doug Barton :
I have considered changing the order of how portmaster does things from:
build
backup package (unless -B)
deinstall
install
to:
backup package
deinstall
build
install
That is undoubtedly more dangerous, and would require the "automated
backout"
On Wed, 5 Aug 2009, Doug Barton wrote:
Naram Qashat wrote:
Actually, I had this problem as well, I found the solution (after a bit
of Googling), is to deinstall devel/dbus-qt4 and then install it again.
Apparently the update conflicts with the older version already installed.
Oy, that's not
43 matches
Mail list logo
