David T-G wrote on 27.08.2011 00:56:
=> No MD5 checksum recorded for sc-7.16.tar.gz.
=> No suitable checksum found for sc-7.16.tar.gz.
Oh, MD5 checksums was deprecated some time ago, so it looks
like you have very old ports tree. Please consult this page
on how to update:
http://www.fr
David T-G wrote on 27.08.2011 00:59:
Ruslan, et al --
...and then David T-G said...
%
...
% In the mean time, since this looks like an ordinary tarball of source
% code, I'll try extracting it in a tmp dir and doing a regular manual
% build.
That worked just fine; woo hoo! Thanks so much for t
I had ghostscript8 installed, but after an ordinary upgrade (I think, I mean,
I don't recall doing anything unusual), I ended up with ghostscript9. After
that, portmaster complained that ghostscript8 was a dependency for a couple of
the other installed ports:
$ portmaster --check-depends
[...]
On Fri, 2011-08-26 at 18:51 -0400, Carmel wrote:
> I found the problem. I had downloaded the source files for BSD a few
> days ago; however, I never rebuild the kernel or world. When the nvidia
> driver got rebuild it was evidently using those new files. I got the
> answer while Googling. When try
I'm going to speak for myself and not portmgr here.
My take has always been that looking through the Ports Collection should
be done by some high-level search tool (e.g. website). Just looking
through the raw portnames, even if they have descriptions, is mind-
numbing.
I don't believe that we sh
On Fri, 26 Aug 2011 17:23:28 -0500
Conrad J. Sabatier articulated:
> On Fri, 26 Aug 2011 15:30:47 -0400
> Carmel wrote:
>
> > After updating my system as per the UPDATING file, I now find that
> > the Nvidia driver no longer works with Xorg.
>
> [snip]
>
> Hmm, very strange. I've been updatin
On Fri, 26 Aug 2011 15:30:47 -0400
Carmel wrote:
> After updating my system as per the UPDATING file, I now find that the
> Nvidia driver no longer works with Xorg.
[snip]
Hmm, very strange. I've been updating ports left and right the last
couple of days (including both libproxy and libnotify)
Has portmgr considered a re-organization of the current
directory structure for ports?
troutmask:root[226] pwd
/usr/ports/devel
troutmask:root[227] ls | wc -l
3633
troutmask:root[228] ls | grep -E ^p5- | wc -l
1446
troutmask:root[229] ls | grep -E ^py- | wc -l
275
troutmask:root[230]
Ruslan, et al --
...and then David T-G said...
%
...
% In the mean time, since this looks like an ordinary tarball of source
% code, I'll try extracting it in a tmp dir and doing a regular manual
% build.
That worked just fine; woo hoo! Thanks so much for the pointer.
If you get any answers fo
Ruslan, et al --
...and then Ruslan Mahmatkhanov said...
%
% David T-G wrote on 26.08.2011 21:44:
% >
% >I would like to compile sc, the spreadsheet calculator, but I am having
% >trouble with the port. The port on my system for 6.21 cannot find the
...
%
% It's strange enough. All is fine for
Howdy,
Doing some port updates and noticed that mail/postfix-policyd-spf relies
on mail/libspf2-10, which according to
http://portaudit.FreeBSD.org/2ddbfd29-a455-11dd-a55e-00163e16.html
is vulnerable. There is a port of mail/libspf2 which is not vulnerable,
is it possible to update mail/postfi
On 08/26/2011 12:30, Carmel wrote:
> After updating my system as per the UPDATING file, I now find that the
> Nvidia driver no longer works with Xorg.
Did you rebuild the nvidia module?
--
Nothin' ever doesn't change, but nothin' changes much.
-- OK Go
On Fri, Aug 26, 2011 at 03:30:47PM -0400, Carmel wrote:
> After updating my system as per the UPDATING file, I now find that the
> Nvidia driver no longer works with Xorg.
Does it happen with the latest stable version from the nvidia.com? I have
some pending patches in my queue for the port, but
After updating libproxy-0.4.6 as per the directions in UPDATING, the
claws-mail-fancy plugin crashes. Libproxy is required by
claws-mail-fancy:
pkg_info -R libproxy*
Information for libproxy-0.4.6:
Required by:
{snip}
claws-mail-fancy-0.9.13_1
Since that is the only thing that has materially ch
After updating my system as per the UPDATING file, I now find that the
Nvidia driver no longer works with Xorg.
From the Xorg.0.log file
(EE) Aug 26 14:46:20 NVIDIA(0): Failed to initialize the NVIDIA kernel
module. Please see the (EE) Aug 26 14:46:20 NVIDIA(0): system's
kernel log for additi
David T-G wrote on 26.08.2011 21:44:
Johan --
I would like to compile sc, the spreadsheet calculator, but I am having
trouble with the port. The port on my system for 6.21 cannot find the
sources when it goes to download. I searched the ports list and found
the 7.16 port listed (with your name
Johan --
I would like to compile sc, the spreadsheet calculator, but I am having
trouble with the port. The port on my system for 6.21 cannot find the
sources when it goes to download. I searched the ports list and found
the 7.16 port listed (with your name as the maintainer), but could not
down
Hello, my name is Mihail Suhorosov, Im from Russia and I
use you port for FreeBSD freevrrpd.(My BSD version is 8.2)
I have some problem. I can't start this programm. My
config is:
[VRID]
serverid = 1
interface = re0
priority = 255
addr = 10.50.40.8/32
#masterscript = /usr/local/bin/master_scri
2011/8/26 Jimmie James :
> libnotify-0.7.3_1
> notification-daemon-0.7.1
> FreeBSD jimmiejaz.org 8.2-STABLE FreeBSD 8.2-STABLE #0: Sun Jun 26 08:42:45
> EDT 2011 jim...@jimmiejaz.org:/usr/obj/usr/src/sys/FORTYTWO i386
>
> After following the portupgrade steps to update libnotify and libproxy
>
libnotify-0.7.3_1
notification-daemon-0.7.1
FreeBSD jimmiejaz.org 8.2-STABLE FreeBSD 8.2-STABLE #0: Sun Jun 26
08:42:45 EDT 2011 jim...@jimmiejaz.org:/usr/obj/usr/src/sys/FORTYTWO
i386
After following the portupgrade steps to update libnotify and libproxy
(notification-daemon got rebuild
Koop Mast wrote on 24.08.2011 16:20:
On Wed, 2011-08-24 at 14:45 +0400, Ruslan Mahmatkhanov wrote:
ajtiM wrote on 24.08.2011 14:38:
Stop in /usr/ports/graphics/gimp-gmic-plugin.
*** Error code 1
Stop in /usr/ports/graphics/gimp-gmic-plugin.
===>>> make failed for graphics/gimp-gmic-plugin
Am 25.08.2011 16:05, schrieb Jerry:
> On Thu, 25 Aug 2011 07:47:50 -0400
> Robert Huff articulated:
>
>> Jerry writes:
>>
>>> That did not actually answer my question(s). Exactly why is the
>>> port being reverted to 1.8 as the default;
>>
>> Insufficient testing for whether 1.9 works with
Peter Jeremy wrote on 26.08.2011 09:05:
I am having problems building devel/gobject-introspection on one
9.0-BETA1 host. I can build it without problems on 8.2 and another
9.0-BETA1 box. In all cases, I'm using gcc and amd64. The failure
is:
GISCAN GLib-2.0.gir
g-ir-scanner: GLib: warning: 48
Stanislav Sedov writes:
> Meanwhile, we continue to work on fixing the major issued people
> reported (some portupgrade glitches, ability to use the newer
> ruby-gems under ruby 1.9), and hopefully we'll be able to make it
> default again soon enough.
Is there an estimate - even a ro
Peter Jeremy wrote on 26.08.2011 09:05:
I am having problems building devel/gobject-introspection on one
9.0-BETA1 host. I can build it without problems on 8.2 and another
9.0-BETA1 box. In all cases, I'm using gcc and amd64. The failure
is:
[skipped]
Note that if I go to the work director
Is anyone working on a dbmail v3 port. As the current maintainer is not
responding I've created a local development version which appears to
compile and run though there are issues that I've raised with the DBMail
bugtracker to do with mhash redefinitions causing the dbmail version to
display
On 26 August 2011 07:51, Ruslan Mahmatkhanov wrote:
> Chris Rees wrote on 25.08.2011 19:52:
>>
>> On 25 August 2011 14:27, Ruslan Mahmatkhanov wrote:
>>>
>>> Chris Rees wrote on 25.08.2011 16:51:
On 25 August 2011 13:44, Ruslan Mahmatkhanov
wrote:
>
> How to correctly remo
27 matches
Mail list logo
