Ed Schouten wrote:
Hello everyone,
This morning I ran a `readelf -d' on an application that I maintain
...
I've added a bunch of patches for the ports I use for audio/herrie. I
didn't file any PR's yet, because I'd like to hear your opinions on this
matter. Are my findings correct?
Roger
Andriy Gapon wrote:
And a practical thought: it seems that in recent FreeBSD versions system
tar can work rather well with the ISO CD9660 FS, so it should be enough
to list directories in an image. What I am trying to say: before adding
a dependency examine your options and choose the best one.
On Mon, 2007-12-24 at 13:28 -0600, Scott T. Hildreth wrote:
> ===> Extracting for evolution-2.12.2
> => MD5 Checksum OK for gnome2/evolution-2.12.2.tar.bz2.
> => SHA256 Checksum OK for gnome2/evolution-2.12.2.tar.bz2.
> ===> Patching for evolution-2.12.2
> ===> Applying FreeBSD patches for evol
Synopsis: Update port: sysutils/p5-Unix-Mknod
Responsible-Changed-From-To: pirzyk->freebsd-ports
Responsible-Changed-By: pirzyk
Responsible-Changed-When: Mon Dec 24 20:04:11 UTC 2007
Responsible-Changed-Why:
Approval to commit update.
http://www.freebsd.org/cgi/query-pr.cgi?pr=119000
_
Scott T. Hildreth wrote:
===> Extracting for evolution-2.12.2
=> MD5 Checksum OK for gnome2/evolution-2.12.2.tar.bz2.
=> SHA256 Checksum OK for gnome2/evolution-2.12.2.tar.bz2.
===> Patching for evolution-2.12.2
===> Applying FreeBSD patches for evolution-2.12.2
===> evolution-2.12.2 depends
===> Extracting for evolution-2.12.2
=> MD5 Checksum OK for gnome2/evolution-2.12.2.tar.bz2.
=> SHA256 Checksum OK for gnome2/evolution-2.12.2.tar.bz2.
===> Patching for evolution-2.12.2
===> Applying FreeBSD patches for evolution-2.12.2
===> evolution-2.12.2 depends on executable: gmake - fou
--On December 24, 2007 4:23:15 PM +0200 Andriy Gapon <[EMAIL PROTECTED]>
wrote:
And a practical thought: it seems that in recent FreeBSD versions system
tar can work rather well with the ISO CD9660 FS, so it should be enough
to list directories in an image. What I am trying to say: before adding
Quoting Umar <[EMAIL PROTECTED]>:
Dear Stefan!
Thanks for your reply!
touch /var/db/pkg/squid-/+IGNOREME.
I already done that. But its not working, here is the error message.
===>>> The www/squid25 port has been deleted: Has expired: This version is
no longer supported by the developers
=
Dear Stefan!
Thanks for your reply!
> touch /var/db/pkg/squid-/+IGNOREME.
I already done that. But its not working, here is the error message.
===>>> The www/squid25 port has been deleted: Has expired: This version is
no longer supported by the developers
===>>> Aborting update
===>>> Child pr
Paul Schmehl wrote:
> --On Monday, December 10, 2007 16:33:20 +0200 Andriy Gapon
> <[EMAIL PROTECTED]> wrote:
>>
>>> From a small research it seems that the only thing needed from cdrtools
>> is isoinfo utility which gets called in FreeBSD-specific code
>> (hald/freebsd/probing/probe-volume.c) li
On Mon, Dec 24, 2007 at 03:47:56AM -0800, Umar wrote:
>
> Hi All,
>
> I am using portmaster for updating my existing ports. How I can bypass a
> specific package e.g (squid) I don't want to upgrade this package during
> ports upgrading through portmaster.
>
> So please help me what should i do?
Hi All,
I am using portmaster for updating my existing ports. How I can bypass a
specific package e.g (squid) I don't want to upgrade this package during
ports upgrading through portmaster.
So please help me what should i do?
Regards,
Umar Draz
--
View this message in context:
http://www.nab
Current FreeBSD problem reports
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including experimental
development code and obsolete releases.
Bugs can be in one of several states:
o - open
A problem report has bee
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
Hi ,
Wish everyone a happy and MerryChristmas.
Please look at the startling facts and snippets of information collected by our
team of writers this christmas and share them with your friends and add your
own comments and ideas .
http://www.writerslinkup.com/christmas_facts.php
Merry Christ
20 matches
Mail list logo
