Re: determining what ports directly depend on X
On 1/3/08, Frank J. Laszlo <[EMAIL PROTECTED]> wrote:
> Aryeh Friedman wrote:
> > On 1/3/08, Frank J. Laszlo <[EMAIL PROTECTED]> wrote:
> >
> >> Aryeh Friedman wrote:
> >>
> >>> I need to determine which ports depend directly (i.e. they have it
> >>> listed as a B/RDEPS). The specfic task I am working on right now
> >>> (but this will need to be more general later) is attempting to find
> >>> all the direct childern of libtool15
> >>>
> >>>
> >> A quick hack would be
> >>
> >> grep libtool-1.5 /usr/ports/INDEX-6| awk -F"|" {'print $2'}
> >>
> >
> >
> > Doesn't quite work because it appears index is equiv to "make missing"
> > which includes indirect parents. For example x11-wm/compwiz does not
> > reference libool-1.5 except in a USE= line.
> >
>
> Most ports should be setup to use "USE_AUTOTOOLS", but obviously there
> are a few strays.
>
> Anything that uses USE_AUTOTOOLS should have LIBTOOL_DEPENDS defined.
> You could check this. to collect the strays, grepping through for
> ^.*DEPENDS=.*libtool15" should pick them up.
Completely useless... it catchs stuff I know for a fact has no direct
dependancy on libtool15... for example I am the author (but not the
maintainer but I helped in the port creation) of devel/thistest and
the *ONLY* direct dependancy it has is java/jdk16 it still lists
libtool-1.5 as a depend in INDEX-8
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH] portmaster with SU_CMD
On Thu, 03 Jan 2008 19:46:49 -0600, Jo Rhett <[EMAIL PROTECTED]> wrote: On Nov 12, 2007, at 8:33 AM, Jeremy Messenger wrote: I agree, because you can't build any ports in /usr/ports as in normal user anyway. I don't see any good reason to do it either. Huh? In 5 years of using FreeBSD I've never built a single port as root. What are you talking about? You can't by default in /usr/ports. (I have installed them as root, but you said "build") -- [EMAIL PROTECTED] - [EMAIL PROTECTED] FreeBSD GNOME Team - FreeBSD Multimedia Hat (ports, not src) http://www.FreeBSD.org/gnome/ - [EMAIL PROTECTED] http://wiki.freebsd.org/multimedia - [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: determining what ports directly depend on X
On 1/3/08, Frank J. Laszlo <[EMAIL PROTECTED]> wrote:
> Aryeh Friedman wrote:
> > On 1/3/08, Frank J. Laszlo <[EMAIL PROTECTED]> wrote:
> >
> >> Aryeh Friedman wrote:
> >>
> >>> I need to determine which ports depend directly (i.e. they have it
> >>> listed as a B/RDEPS). The specfic task I am working on right now
> >>> (but this will need to be more general later) is attempting to find
> >>> all the direct childern of libtool15
> >>>
> >>>
> >> A quick hack would be
> >>
> >> grep libtool-1.5 /usr/ports/INDEX-6| awk -F"|" {'print $2'}
> >>
> >
> >
> > Doesn't quite work because it appears index is equiv to "make missing"
> > which includes indirect parents. For example x11-wm/compwiz does not
> > reference libool-1.5 except in a USE= line.
> >
>
> Most ports should be setup to use "USE_AUTOTOOLS", but obviously there
> are a few strays.
>
> Anything that uses USE_AUTOTOOLS should have LIBTOOL_DEPENDS defined.
> You could check this. to collect the strays, grepping through for
> ^.*DEPENDS=.*libtool15" should pick them up.
>
> Hope this helps.
For various reasons I deleted /usr/ports (in prep to repopulate it
from a local cvs repo) so can't test this right now... but the orginal
question is due to a PR I will be filing as soon I have a working
browser on the machine in question... the PR is that if you install
libtool-1.5 under 8-current (amd64 only???) it will incorrectly ID the
installed OS and give errors about "freebsd-" not being defined as a
platform type... the hand fix is to find the line that has that and
add -elf to it but the root cause is something about 8-current makes
it so it is ID'ed wrong.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: determining what ports directly depend on X
Aryeh Friedman wrote:
On 1/3/08, Frank J. Laszlo <[EMAIL PROTECTED]> wrote:
Aryeh Friedman wrote:
I need to determine which ports depend directly (i.e. they have it
listed as a B/RDEPS). The specfic task I am working on right now
(but this will need to be more general later) is attempting to find
all the direct childern of libtool15
A quick hack would be
grep libtool-1.5 /usr/ports/INDEX-6| awk -F"|" {'print $2'}
Doesn't quite work because it appears index is equiv to "make missing"
which includes indirect parents. For example x11-wm/compwiz does not
reference libool-1.5 except in a USE= line.
Most ports should be setup to use "USE_AUTOTOOLS", but obviously there
are a few strays.
Anything that uses USE_AUTOTOOLS should have LIBTOOL_DEPENDS defined.
You could check this. to collect the strays, grepping through for
^.*DEPENDS=.*libtool15" should pick them up.
Hope this helps.
-Frank Laszlo
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: determining what ports directly depend on X
On 1/3/08, Frank J. Laszlo <[EMAIL PROTECTED]> wrote:
> Aryeh Friedman wrote:
> > I need to determine which ports depend directly (i.e. they have it
> > listed as a B/RDEPS). The specfic task I am working on right now
> > (but this will need to be more general later) is attempting to find
> > all the direct childern of libtool15
> >
> A quick hack would be
>
> grep libtool-1.5 /usr/ports/INDEX-6| awk -F"|" {'print $2'}
Doesn't quite work because it appears index is equiv to "make missing"
which includes indirect parents. For example x11-wm/compwiz does not
reference libool-1.5 except in a USE= line.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: determining what ports directly depend on X
Aryeh Friedman wrote:
I need to determine which ports depend directly (i.e. they have it
listed as a B/RDEPS). The specfic task I am working on right now
(but this will need to be more general later) is attempting to find
all the direct childern of libtool15
A quick hack would be
grep libtool-1.5 /usr/ports/INDEX-6| awk -F"|" {'print $2'}
Regards,
Frank Laszlo
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
determining what ports directly depend on X
I need to determine which ports depend directly (i.e. they have it listed as a B/RDEPS). The specfic task I am working on right now (but this will need to be more general later) is attempting to find all the direct childern of libtool15 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH] portmaster with SU_CMD
On Nov 12, 2007, at 12:04 PM, Jeremy Messenger wrote: I don't count this as a good reason, since there is no reason to do it in complicate way for portmaster. The portmaster required root for install, so why not just login as in root and run portmaster? So why does the ports tree currently allow you to run "make install" as non-root and escalate when necessary? Exactly. You do have a good point but I have yet to see configure/build will mess up the filesystem, which Heh, if I cared enough I could dig up a few dozen examples. Most people aren't good scripters. Even fewer are good at autoconf, and voila you get runaway commands that import the root directory and execute it... place) around in / filesystem a few of times. Kind of no difference. Big difference. Easy to read install: before running make. Hard to read autoconf scripts. -- Jo Rhett senior geek Silicon Valley Colocation Support Phone: 408-400-0550 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH] portmaster with SU_CMD
I'm sorry, Garrett. I don't follow your logic. Installing as root can leave holes, so instead you should build AND install as root? Where exactly is this more secure? On Nov 12, 2007, at 10:24 AM, Garrett Cooper wrote: Greg Minshall wrote: i'd add my two cents for being able to do builds without running as root. Building as non-root user and then installing as root has its caveats I would think.. Pro: - Compiling as a non-root user and then installing as root reduces the security risk of a possible exploit in the portmaster / base system infrastructure. Con: - People with sufficient permissions (possibly caused by bad umask settings) but without root access, can modify the binaries / recompile files to suit their needs prior to them being installed as root (say modify the source's logic to suit one's needs, i.e. skip a critical step or install a hardcoded backdoor). Don't think that this isn't a problem because many ports take a long time to compile, and as such there are plenty of chances to inject whatever code one wants so that it's installed. - The same goes for reinstalls, because if I knew that a user didn't clean out their compiled sources (don't remember if portmaster does this; portupgrade / portinstall do this though), and someone recompiled a portion of the binaries and the maintaining user didn't check that the binaries had been untouched since the last compile / install, they would be in serious trouble. It's not entirely likely but given some peoples' resources and knowledge, and if they were either rubbed the wrong way, or wanted to make sure they had access to the machine at all times, this would definitely be a potential issue. Personally, I don't really care either way because no one has access to my machines, either locally or remotely, but I would think that these are issues to consider before going all gung ho with this patch. Sometimes you gotta think as a system cracker (consider security faults), before you start thinking like a hacker (trying to fix things). -Garrett ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports- [EMAIL PROTECTED]" -- Jo Rhett senior geek Silicon Valley Colocation Support Phone: 408-400-0550 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH] portmaster with SU_CMD
On Nov 12, 2007, at 8:33 AM, Jeremy Messenger wrote: I agree, because you can't build any ports in /usr/ports as in normal user anyway. I don't see any good reason to do it either. Huh? In 5 years of using FreeBSD I've never built a single port as root. What are you talking about? (I have installed them as root, but you said "build") -- Jo Rhett senior geek Silicon Valley Colocation Support Phone: 408-400-0550 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [PATCH] portmaster with SU_CMD
On Nov 11, 2007, at 2:59 PM, Doug Barton wrote: This is very interesting stuff, but I don't see how it would be useful to a very wide audience. My feeling is that the vast majority of our users build and/or install ports as root, and I don't see any good reason for that not to be the default practice. Heh. If you weren't Doug Barton, I'd wonder just how often you build random ports. Lots of them have very broken install scripts. I *never* build or install ports as root unless the package's install is too broken to escalate properly and then I assume that everything else is broken too and read it carefully by hand. I'll review your patch more thoroughly when time allows (since we are in a freeze I can't add new features right now anyway) but I'm not inclined to add this unless there is a fairly substantial clamor for it. clam clam clam... -- Jo Rhett senior geek Silicon Valley Colocation Support Phone: 408-400-0550 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: unknown build error
thanks, but my date seems to be OK # date Fri Jan 4 01:45:35 CET 2008 and still doesn't work. --- On Thu 01/03, Mark Kirkwood < [EMAIL PROTECTED] > wrote: From: Mark Kirkwood [mailto: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], freebsd-ports@freebsd.org Date: Fri, 04 Jan 2008 12:39:26 +1300 Subject: Re: unknown build error I wrote:> Piotr wrote:>> is it there any solution to install p5-Net-Pcap from ports without >> errors ?>> parameter.> Checking if your kit is complete...> Looks good> >> 'LICENSE' is not a known MakeMaker parameter name.> Writing Makefile >> for Net::Pcap> ==> Your Makefile has been rebuilt. <==> ==> Please >> rerun the make command. <==> false> *** Error code 1> > Stop in >> /usr/ports/net/p5-Net-Pcap/work/Net-Pcap-0.15.> *** > Error code 1> > >> Stop in /usr/ports/net/p5-Net-Pcap.This often means your clock is >> [EMAIL PROTECTED] >> mailing > As Kris said, this is most likely due to your clock being wrong - i.e > your system date/time is probably set incorrectly (what does 'date' > say, and is the timezone set correctly?). If not you need to fix it/them.>> I have had this happen once where *my* system date/time was correct > but the server I fetched the files from was not... i.e they were > future dated... similar result! This is unlikely to be the case here, > but (only if your system date is correct) you can check for this by > extracting the relevant distfile for p5_Net_Pcap and checking the > dates on the files.>Piotr,Sorry - I should have read the preceding message, you seem to have fixed the clock issue...pls ignore!MarkP.s:You mail client does horrible things to quoted messageswhich makes it a bit confusing to read! ___ Join Excite! - http://www.excite.com The most personalized portal on the Web! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: unknown build error
I wrote: Piotr wrote: is it there any solution to install p5-Net-Pcap from ports without errors ? parameter.> Checking if your kit is complete...> Looks good> 'LICENSE' is not a known MakeMaker parameter name.> Writing Makefile for Net::Pcap> ==> Your Makefile has been rebuilt. <==> ==> Please rerun the make command. <==> false> *** Error code 1> > Stop in /usr/ports/net/p5-Net-Pcap/work/Net-Pcap-0.15.> *** > Error code 1> > Stop in /usr/ports/net/p5-Net-Pcap.This often means your clock is [EMAIL PROTECTED] mailing As Kris said, this is most likely due to your clock being wrong - i.e your system date/time is probably set incorrectly (what does 'date' say, and is the timezone set correctly?). If not you need to fix it/them. I have had this happen once where *my* system date/time was correct but the server I fetched the files from was not... i.e they were future dated... similar result! This is unlikely to be the case here, but (only if your system date is correct) you can check for this by extracting the relevant distfile for p5_Net_Pcap and checking the dates on the files. Piotr, Sorry - I should have read the preceding message, you seem to have fixed the clock issue...pls ignore! Mark P.s: You mail client does horrible things to quoted messageswhich makes it a bit confusing to read! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cannot install p5-Net-Pcap
hi I cannot install p5-Net-Pcap on freeBSD 6.2 due to the following errors: # cd /usr/ports/net/p5-Net-Pcap # make install clean ===> Building for p5-Net-Pcap-0.15_1 cc -c-O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe -DVERSION=\"0.15\" -DXS_VERSION=\"0.15\" -DPIC -fPIC "-I/usr/local/lib/perl5/5.8.8/mach/CORE" -DHAVE_PCAP_LIST_DATALINKS -DHAVE_BLANK -DHAVE_PCAP_LIB_VERSION Pcap.c In file included from Pcap.xs:43: stubs.inc:85:2: warning: #warning "the function pcap_findalldevs() is not available, but will be emulated" In file included from Pcap.xs:43: stubs.inc:91: error: redefinition of `struct pcap_if' stubs.inc:113:2: warning: #warning "the function pcap_breakloop() is not available" stubs.inc:127:2: warning: #warning "the function pcap_setnonblock() is not available" stubs.inc:142:2: warning: #warning "the function pcap_getnonblock() is not available" stubs.inc:157:2: warning: #warning "the function pcap_dump_file() is not available" stubs.inc:172:2: warning: #warning "the function pcap_dump_flush() is not available" stubs.inc:202:2: warning: #warning "the function pcap_set_datalink() is not available" stubs.inc:217:2: warning: #warning "the function pcap_datalink_name_to_val() is not available" stubs.inc:232:2: warning: #warning "the function pcap_datalink_val_to_name() is not available" stubs.inc:247:2: warning: #warning "the function pcap_datalink_val_to_description() is not available" stubs.inc:262:2: warning: #warning "the function pcap_compile_nopcap() is not available" stubs.inc:277:2: warning: #warning "the function pcap_get_selectable_fd() is not available" stubs.inc:292:2: warning: #warning "the function pcap_next_ex() is not available" stubs.inc:307:2: warning: #warning "the function pcap_sendpacket() is not available" stubs.inc:322:2: warning: #warning "the function pcap_createsrcstr() is not available" stubs.inc:337:2: warning: #warning "the function pcap_parsesrcstr() is not available" stubs.inc:352:2: warning: #warning "the function pcap_open() is not available" stubs.inc:373:2: warning: #warning "the function pcap_setbuff() is not available" stubs.inc:388:2: warning: #warning "the function pcap_setuserbuffer() is not available" stubs.inc:403:2: warning: #warning "the function pcap_setmode() is not available" stubs.inc:418:2: warning: #warning "the function pcap_setmintocopy() is not available" stubs.inc:433:2: warning: #warning "the function pcap_sendqueue_alloc() is not available" stubs.inc:455:2: warning: #warning "the function pcap_sendqueue_destroy() is not available" stubs.inc:469:2: warning: #warning "the function pcap_sendqueue_queue() is not available" stubs.inc:484:2: warning: #warning "the function pcap_sendqueue_transmit() is not available" stubs.inc:499:2: warning: #warning "the function pcap_event() is not available" stubs.inc:514:2: warning: #warning "the function pcap_setsampling() is not available" Pcap.c: In function `XS_Net__Pcap_dump_open': Pcap.c:541: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_setnonblock': Pcap.c:574: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_getnonblock': Pcap.c:624: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_dispatch': Pcap.c:676: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_loop': Pcap.c:724: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_next': Pcap.c:767: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_next_ex': Pcap.c:831: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_dump': Pcap.c:898: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_compile': Pcap.c:970: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_setfilter': Pcap.c:1050: warning: cast to pointer from integer of different size Pcap.c:1057: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_freecode': Pcap.c:1085: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_breakloop': Pcap.c:1112: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_close': Pcap.c:1139: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_dump_close': Pcap.c:1166: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_dump_file': Pcap.c:1194: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_dump_flush': Pcap.c:1232: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_datalink': Pcap.c:1262: warning: cast to pointer from integer of different size Pcap.c: In function `XS_Net__Pcap_set_datalink': Pcap.c:1293:
Re: unknown build error
Piotr wrote: is it there any solution to install p5-Net-Pcap from ports without errors ? parameter.> Checking if your kit is complete...> Looks good> 'LICENSE' is not a known MakeMaker parameter name.> Writing Makefile for Net::Pcap> ==> Your Makefile has been rebuilt. <==> ==> Please rerun the make command. <==> false> *** Error code 1> > Stop in /usr/ports/net/p5-Net-Pcap/work/Net-Pcap-0.15.> *** > Error code 1> > Stop in /usr/ports/net/p5-Net-Pcap.This often means your clock is [EMAIL PROTECTED] mailing As Kris said, this is most likely due to your clock being wrong - i.e your system date/time is probably set incorrectly (what does 'date' say, and is the timezone set correctly?). If not you need to fix it/them. I have had this happen once where *my* system date/time was correct but the server I fetched the files from was not... i.e they were future dated... similar result! This is unlikely to be the case here, but (only if your system date is correct) you can check for this by extracting the relevant distfile for p5_Net_Pcap and checking the dates on the files. Cheers Mark ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: maintainer change for cfengine?
Jo Rhett píše v čt 03. 01. 2008 v 12:03 -0800: > Patches for cfengine port are stacking up. The port is two versions > behind, and there are critical bugfixes in those versions. Can we > get the maintainer changed for the cfengine ports? > > You can see all of the open bugs at > http://www.freebsd.org/cgi/query-pr-summary.cgi?text=cfengine > > I can do it. Others have offered. Anyone who has time to follow up > would be fine. delphij filed the last PR on this port, and it's already past maintainer timeout, so there's nothing preventing him from committing it. -- Pav Lucistnik <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> > Why do we need a film of "Lord of the Rings" when we have the book? Because watching a cg enhanced Legolas fire a flaming arrow into the heart of a warg is cool? - [EMAIL PROTECTED] in rec.games.roguelike.angband signature.asc Description: Toto je digitálně podepsaná část zprávy
white_dune security problems
Hi ! There are a buffer overflow and a format string error, all versions of white_dune older than 0.29beta795 and 0.28pl13 should not be used. This also includes dune-0.13 (white_dune is a fork of dune-0.13). Unfortunatly, the security problems are located in errormessage routines, so it is rather simple to build a exploit 8-( Versions currently available without this problems are http://129.69.35.12/dune/white_dune-0.29beta796.tar.gz for the development version and http://129.69.35.12/dune/white_dune-0.28pl13.tar.gz for the stable version. The major difference between the development and the stable tree is: - the development version contains much more features and bugfixes - the user documentation of the development version and the stable version is almost idenitical 8-( see also http://www.securityfocus.com/archive/1/485724 so long MUFTI -- "Self-destruct in 5 seconds. Have a nice day...\n"); from /usr/src/linux/fs/super.c ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
maintainer change for cfengine?
Patches for cfengine port are stacking up. The port is two versions behind, and there are critical bugfixes in those versions. Can we get the maintainer changed for the cfengine ports? You can see all of the open bugs at http://www.freebsd.org/cgi/query-pr-summary.cgi?text=cfengine I can do it. Others have offered. Anyone who has time to follow up would be fine. -- Jo Rhett senior geek Silicon Valley Colocation Support Phone: 408-400-0550 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: about old ports
On Thu, Jan 03, 2008 at 04:15:25PM -0200, Expresso Digital ISP wrote: > Hi, my name is Cesar and I like to know how can I do to install an old port? > I update the ports with portsnap, but I have to install mysql-server-5.1.11, > because my system works with this database version. You'll probably want to use ports-mgmt/portdowngrade which will checkout an old version of your specification. Your other option is to manually check it out from anoncvs by hand. -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
INDEX now builds successfully on 5.x
___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
about old ports
Hi, my name is Cesar and I like to know how can I do to install an old port? I update the ports with portsnap, but I have to install mysql-server-5.1.11, because my system works with this database version. Regards -- Att. Expresso Digital ISP - tecnologia.multimidia.seguranca Cesar Vogelsanger MCSO - Módulo Certified Security Officer Administrador de Tecnologia Divisão de Segurança da Informação Joinville - SC - Brasil +55 (47) 3433-1516 e-mail: [EMAIL PROTECTED] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
(pas de sujet)
plop. Teta. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
INDEX build failed for 5.x
INDEX build failed with errors: Generating INDEX-5 - please wait..pkg_info: not found pkg_info: not found pkg_info: not found Done. make_index: gnome-gmail-notifier-0.9.1: no entry for /usr/ports/security make_index: gnome-gmail-notifier-0.9.1: no entry for /usr/ports/security Committers on the hook: bms flz lth miwi mm mnag pav rafan Most recent CVS update was: U audio/akode/Makefile U devel/Makefile U devel/piklab/Makefile U devel/piklab/distinfo U devel/piklab/pkg-descr U devel/piklab/pkg-plist U dns/noip/Makefile U dns/noip/pkg-plist U dns/noip/files/noip.in U dns/noip/files/pkg-message.in U mail/Makefile U mail/gmime2/Makefile U mail/gmime2/distinfo U mail/gmime2/files/patch-docs_Makefile.in U mail/gnome-gmail-notifier/Makefile U mail/gnome-gmail-notifier/distinfo U mail/gnome-gmail-notifier/pkg-descr U mail/gnome-gmail-notifier/pkg-plist U net/xmlrpc-c/Makefile U net/xmlrpc-c/distinfo U net-im/jabberd/Makefile U net-im/jabberd/files/jabberd.in U net-mgmt/nagiosgraph/Makefile U net-mgmt/nagiosgraph/distinfo U net-mgmt/smokeping/Makefile ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports/119290: update of editors/emacs-devel to a new cvs snapshot
Synopsis: update of editors/emacs-devel to a new cvs snapshot Responsible-Changed-From-To: freebsd-ports->freebsd-ports-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jan 3 16:05:40 UTC 2008 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=119290 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ports/119290: update of editors/emacs-devel to a new cvs snapshot
Synopsis: update of editors/emacs-devel to a new cvs snapshot Responsible-Changed-From-To: keramida->freebsd-ports Responsible-Changed-By: keramida Responsible-Changed-When: Thu Jan 3 15:47:26 UTC 2008 Responsible-Changed-Why: Return to the pool of 'ports' PRs. I am not a Ports committer, so someone more experienced will have to approve this. http://www.freebsd.org/cgi/query-pr.cgi?pr=119290 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Updating of pots db causes a dependency error
On Thu, 3 Jan 2008 16:30:33 +0100, Helko Glathe wrote > Updating the ports db causes an error: > > " > [EMAIL PROTECTED] /usr/ports/audio]# portsdb -uU > Updating the ports index ... Generating INDEX.tmp - please > wait..akode-2.0.1,1: "/usr/ports/audio/akode-plugins-polypaudio" > non-existent -- dependency list incomplete > ===> audio/akode failed > *** Error code 1 > 1 error Fixed, thanks for reporting! -- Pav Lucistnik <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Updating of pots db causes a dependency error
Hi Updating the ports db causes an error: " [EMAIL PROTECTED] /usr/ports/audio]# portsdb -uU Updating the ports index ... Generating INDEX.tmp - please wait..akode-2.0.1,1: "/usr/ports/audio/akode-plugins-polypaudio" non-existent -- dependency list incomplete ===> audio/akode failed *** Error code 1 1 error Before reporting this error, verify that you are running a supported version of FreeBSD (see http://www.FreeBSD.org/ports/) and that you have a complete and up-to-date ports collection. (INDEX builds are not supported with partial or out-of-date ports collections -- in particular, if you are using cvsup, you must cvsup the "ports-all" collection, and have no "refuse" files.) If that is the case, then report the failure to [EMAIL PROTECTED] together with relevant details of your ports configuration (including FreeBSD version, your architecture, your environment, and your /etc/make.conf settings, especially compiler flags and WITH/WITHOUT settings). Note: the latest pre-generated version of INDEX may be fetched automatically with "make fetchindex". *** Error code 1 Stop in /usr/ports. *** Error code 1 Stop in /usr/ports. failed to generate INDEX! portsdb: index generation error " My FreeBSD-Version: FreeBSD 6.2-STABLE My Architecture: i386 I've attatched my /etc/make.conf file. Thanks in advance, Helko -- With kind regards Helko Glathe INSTALL_NODEBUG="yes" # wpa_supplicant # # Enable this to include 802.1X and EAP support in wpa_supplicant. # 802.1X with EAP requires openssl but it can be used without to # do things like dynamic WEP keying. The default is to build # wpa_supplicant only with WPA-PSK support. # ENABLE_WPA_SUPPLICANT_EAPOL=true X_WINDOW_SYSTEM=xorg NO_LPR=true WITH_CUPS=yes KERNCONF=MYKERNEL62 WITH_FAM_SYSTEM=gamin WITH_GHOSTSCRIPT_AFPL=yes WITH_MOZILLA=firefox WITH_GECKO=firefox # added by use.perl 2007-11-27 23:37:53 PERL_VER=5.8.8 PERL_VERSION=5.8.8 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: unknown build error
is it there any solution to install p5-Net-Pcap from ports without errors ? --- On Wed 01/02, Piotr < [EMAIL PROTECTED] > wrote: From: Piotr [mailto: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: freebsd-ports@freebsd.org Date: Wed, 2 Jan 2008 21:42:29 -0500 (EST) Subject: Re: unknown build error # ls -l /usr/local/lib/perl5/5.8.8/mach/Config.pm-r--r--r-- 1 root wheel 2567 Jan 3 03:19 /usr/local/lib/perl5/5.8.8/mach/Config.pmI've done perl-after-upgrade, but now I get the following error:# cd /usr/ports/net/p5-Net-Pcap# make install clean===> Building for p5-Net-Pcap-0.15_1cc -c-O2 -fno-strict-aliasing -pipe -O2 -fno-strict-aliasing -pipe-DVERSION=\"0.15\" -DXS_VERSION=\"0.15\" -DPIC -fPIC "-I/usr/local/lib/perl5/5.8.8/mach/CORE" -DHAVE_PCAP_LIST_DATALINKS -DHAVE_BLANK -DHAVE_PCAP_LIB_VERSION Pcap.cIn file included from Pcap.xs:43:stubs.inc:85:2: warning: #warning "the function pcap_findalldevs() is not available, but will be emulated"In file included from Pcap.xs:43:stubs.inc:91: error: redefinition of `struct pcap_if'stubs.inc:113:2: warning: #warning "the function pcap_breakloop() is not available"stubs.inc:127:2: warning: #warning "the function pcap_setnonblock() is not available"stubs.inc:142:2: warning: #warning "the function pcap_getnonblock() is not available"stubs.inc:157:2: warning: #warning "the function pcap_dump_file() is not available"stubs.inc:172:2: warning: #warning "the function pcap_dump_flush() is not available"stubs.inc:202:2: warning: #warning "the function pcap_set_datalink() is not available"stubs.inc:217:2: warning: #warning "the function pcap_datalink_name_to_val() is not available"stubs.inc:232:2: warning: #warning "the function pcap_datalink_val_to_name() is not available"stubs.inc:247:2: warning: #warning "the function pcap_datalink_val_to_description() is not available"stubs.inc:262:2: warning: #warning "the function pcap_compile_nopcap() is not available"stubs.inc:277:2: warning: #warning "the function pcap_get_selectable_fd() is not available"stubs.inc:292:2: warning: #warning "the function pcap_next_ex() is not available"stubs.inc:307:2: warning: #warning "the function pcap_sendpacket() is not available"stubs.inc:322:2: warning: #warning "the function pcap_createsrcstr() is not available"stubs.inc:337:2: warning: #warning "the function pcap_parsesrcstr() is not available"stubs.inc:352:2: warning: #warning "the function pcap_open() is not available"stubs.inc:373:2: warning: #warning "the function pcap_setbuff() is not available"stubs.inc:388:2: warning: #warning "the function pcap_setuserbuffer() is not available"stubs.inc:403:2: warning: #warning "the function pcap_setmode() is not available"stubs.inc:418:2: warning: #warning "the function pcap_setmintocopy() is not available"stubs.inc:433:2: warning: #warning "the function pcap_sendqueue_alloc() is not available"stubs.inc:455:2: warning: #warning "the function pcap_sendqueue_destroy() is not available"stubs.inc:469:2: warning: #warning "the function pcap_sendqueue_queue() is not available"stubs.inc:484:2: warning: #warning "the function pcap_sendqueue_transmit() is not available"stubs.inc:499:2: warning: #warning "the function pcap_event() is not available"stubs.inc:514:2: warning: #warning "the function pcap_setsampling() is not available"Pcap.c: In function `XS_Net__Pcap_dump_open':Pcap.c:541: warning: cast to pointer from integer of different sizePcap.c: In function `XS_Net__Pcap_setnonblock':Pcap.c:574: warning: cast to pointer from integer of different sizePcap.c: In function `XS_Net__Pcap_getnonblock':Pcap.c:624: warning: cast to pointer from integer of different sizePcap.c: In function `XS_Net__Pcap_dispatch':Pcap.c:676: warning: cast to pointer from integer of different sizePcap.c: In function `XS_Net__Pcap_loop':Pcap.c:724: warning: cast to pointer from integer of different sizePcap.c: In function `XS_Net__Pcap_next':Pcap.c:767: warning: cast to pointer from integer of different sizePcap.c: In function `XS_Net__Pcap_next_ex':Pcap.c:831: warning: cast to pointer from integer of different sizePcap.c: In function `XS_Net__Pcap_dump':Pcap.c:898: warning: cast to pointer from integer of different sizePcap.c: In function `XS_Net__Pcap_compile':Pcap.c:970: warning: cast to pointer from integer of different sizePcap.c: In function `XS_Net__Pcap_setfilter':Pcap.c:1050: warning: cast to pointer from integer of different sizePcap.c:1057: warning: cast to pointer from integer of different sizePcap.c: In function `XS_Net__Pcap_freecode':Pcap.c:1085: warning: cast to pointer from integer of different sizePcap.c: In function `XS_Net__Pcap_breakloop':Pcap.c:1112: warning: cast to pointer from integer of different sizePcap.c: In function `XS_Net__Pcap_close':Pcap.c:1139: warning: cast to pointer from integer of different sizePcap.c: In function `XS_Net__Pcap_dump_close':Pcap.c:1166: warning: cast to pointer from integer of different si
Re: Maintain PHP4 and MySQL 4.0
On Wed, January 2, 2008 6:34 pm, Xin LI wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Yeongsik Son wrote: >> I'm working at a hosting company, and the company has got lots of >> clients >> who are using PHP4 and MySQL 4.0. >> According to the Makefile of mysql40-server, it seems to be ripped out >> of >> 4.x, but the clients said they had problems with migrate their databases >> to >> 5.x. >> Also, PHP 4.x will be supported unitl August 8, 2008 according to >> PHP.net. >> FreeBSD 6 seems to be supported until May 30, 2010, according to FreeBSD >> Security Advisory, and I wonder that ports maintainers will continue to >> maintain 4.x until that date. >> Do they have the plan of estimated EOL of PHP and MySQL 4.x? >> If you they got, please let me know about it to force or cooperate with >> the >> clients. > Just grabbing one of the replies to the thread: Also note that PHP 4.x will have a security case-by-case ONLY support till that time, it will not be -supported anymore- at all (just on individual cases). Since PHP is an external third party application, please do not mixup the FreeBSD supported versions and ports with eachother. We will support FreeBSD RELENG_6 still May 30, 2010, PHP support for PHP 4.x will vanish at some point (most likely long before 2010). My personal preference would be that we should double-consider whether we want to keep these versions in the ports system (in the foreseeable future) since the versions are no longer regularly supported, mostly likely contain more and more bugs, and are only fixed on a case by case basis, which potentially could cause harm to users using PHP (and MySQL). That said; the period from 4.X to 5.X in both MySQL and PHP form were rather extensive (in my experience) so people should have had the time already to upgrade their software; if not face it that it will be costly if people will find bugs and cannot resolve them anymore for that specific version (support will be more and more expensive), in addition 5.X is mostly backward compatible with 4.x (except for a few things that are not backward compatible). Do what you want ofcourse (And what your business sees as good practise) but I would strongly suggest upgrading to PHP5(.2.5) and MySQL 5.0.51 Thanks, Remko -- /"\ Best regards, | [EMAIL PROTECTED] \ / Remko Lodder | [EMAIL PROTECTED] Xhttp://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
