Re: apache + php + mysql startup order
Hello! On Fri, 1 Dec 2006, Vasil Dimov wrote: On Thu, Nov 30, 2006 at 09:34:11PM +0200, Dmitry Pryanishnikov wrote: And yes, I can just replace # REQUIRE: DAEMON # BEFORE: LOGIN with # REQUIRE: LOGIN in apache.sh, and all works correctly. Yet I prefer (as usually in open-source software world) not to keep local fixes for obvious bugs (and reapply them during every [re]install of apache), but to report them upstream instead. [...] Please submit your patch using send-pr(1) so it does not get overlooked. Done (ports/106429). Vasil Dimov [EMAIL PROTECTED] Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: [EMAIL PROTECTED] nic-hdl: LYNX-RIPE ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Firefox & thunderbird crash saving a file
This started around the late 1.5.0.x versions and also happens in FF 2.0 When saving a file, e.g. an e-mail attachment, right-click->Save Link As... on a webpage, or uploading a file to a web forum, it will work once - maybe twice - but on subsequent saves the dialogue opens but the cursor stays as 'busy' for ~15 seconds, then FF/TB segfault and crash. % uname -a FreeBSD redshift 6.1-RC FreeBSD 6.1-RC #0: Mon May 1 14:05:04 BST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/REDSHIFT i386 This is a stack trace of the core dump - both FF and TB give the same trace. (gdb) bt #0 0x28c0a1ab in pthread_testcancel () from /usr/lib/libpthread.so.2 #1 0x28bf86dd in sigaction () from /usr/lib/libpthread.so.2 #2 0x28bf1c45 in pthread_kill () from /usr/lib/libpthread.so.2 #3 0x28bf14c4 in raise () from /usr/lib/libpthread.so.2 #4 0x08060134 in ?? () #5 0x000b in ?? () #6 0xbfbfb6d0 in ?? () #7 0x in ?? () #8 0x0806e048 in ?? () #9 0x0400 in ?? () #10 0x in ?? () #11 0x in ?? () #12 0x in ?? () #13 0xbfbfb7b0 in ?? () #14 0x000f in ?? () #15 0x in ?? () #16 0x28c0d4b4 in ?? () from /usr/lib/libpthread.so.2 #17 0xbfbfba60 in ?? () #18 0x000b in ?? () #19 0xbfbfb728 in ?? () #20 0x28bf6598 in sigaction () from /usr/lib/libpthread.so.2 Previous frame identical to this frame (corrupt stack?) (gdb) total 19 What is very suspicious is the last line if the trace about a corrupt stack. Looks like it is a threading problem but since I can't find any other posts about this happening I guess it's just my system. Since my system is 6 months old (6.1-RC) do you think doing a make world to bring it up to 6.2 would solve the problem? Thanks. Regards, Mark ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Firefox & thunderbird crash saving a file
On 12/7/06, Mark Ovens <[EMAIL PROTECTED]> wrote: This started around the late 1.5.0.x versions and also happens in FF 2.0 When saving a file, e.g. an e-mail attachment, right-click->Save Link As... on a webpage, or uploading a file to a web forum, it will work once - maybe twice - but on subsequent saves the dialogue opens but the cursor stays as 'busy' for ~15 seconds, then FF/TB segfault and crash. I have also recently experienced this behaviour when doing "Save Image As..." from the shortcut menu in Firefox. I did look at the core file but my conclusions were similar to Mark's - the backtrace was some thousands of frames long and looked corrupted. % uname -a FreeBSD tomo 6.2-RC1 FreeBSD 6.2-RC1 #0: Mon Nov 20 23:48:08 GMT 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TOMO i386 I also had this behaviour on 6.2-PRERELEASE. /JMS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
cups-pstoraster vs. ghostscript 8.15
It looks like both ports install some similar files into share/ghostscript/8.15, in particular share/ghostscript/8.15/lib/gs_init.ps. Frank, could you please look at it or should I mark the two ports as conflicting right away? Thanks! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Unfetchable distfiles reminder
Dear porters, This is just a reminder to please periodically check the list of unfetchable distfiles at http://people.freebsd.org/~fenner/portsurvey/ . In particular, the list of ports with no MAINTAINER with distfile problems, which currently has 223 bad ports, is http://people.freebsd.org/~fenner/portsurvey/[EMAIL PROTECTED] Since no one is responsible for these ports, the problem won't get fixed unless someone on this list takes the initiative. In addition, the list of all ports with any unfetchable distfile is http://people.freebsd.org/~fenner/portsurvey/bad.html if you don't mind coordinating your fixes with the port MAINTAINER. Thanks for your help! Bill "distfiles" Fenner ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: FreeBSD ports: 1 unfetchable distfile: net/smb4k
On Thursday 07 December 2006 16:00, Bill "distfiles" Fenner wrote: > Dear [EMAIL PROTECTED], > > You are listed as the FreeBSD port maintainer for 1 port > whose distfiles are not fetchable from their MASTER_SITES. Could > you please visit > > http://people.freebsd.org/~fenner/portsurvey/[EMAIL PROTECTED] > > and correct the problems listed there? The individual port with > a problem is net/smb4k. Sorry, but port fetchable. to-495:[root] 107>make fetch ===> Vulnerability check disabled, database not found => smb4k-0.7.5.tar.bz2 doesn't seem to exist in /usr/ports/distfiles/. => Attempting to fetch from http://download.berlios.de/smb4k/. smb4k-0.7.5.tar.bz221% of 1774 kB 253 kBps^C fetch: transfer interrupted I had have stop fetch manually here. -- With Best Regards. Rashid N. Achilov (RNA1-RIPE), Web: http://www.askd.ru/~shelton OOO "ACK" telecommunications administrator, e-mail: achilov-rn [at] askd.ru PGP: 83 CD E2 A7 37 4A D5 81 D6 D6 52 BF C9 2F 85 AF 97 BE CB 0A ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Firefox & thunderbird crash saving a file
On Thu, 7 Dec 2006 09:10:05 +, James Seward wrote > On 12/7/06, Mark Ovens <[EMAIL PROTECTED]> wrote: > I also had this behaviour on 6.2-PRERELEASE. Exactly the same bug at home on a 6.2-PRERELEASE :/ Ganaël LAPLANCHE [EMAIL PROTECTED] http://www.martymac.com ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: garne = uneatabl
wreckage of a very armed and deadly machine-you did?, nod yes-good. be less trouble to them if I were safely dead. And there were only pull the swaying bodies back to the deck. vanished. I was wiping my lips with the back of my hand when Ljotur of costume but playing from a wheelchair. If this was to be the last They were good and they took no chances. They were big and mean and I The rest of the band stirred in their sleep when the smoke blew their There was little else I could do until the music was written, the nails. here is the access terminal. Nothing Iron John did seemed to affect the outcome. He was wary, he ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade refusin to upgrade a port .. when it shouldn't imho
On Wed, 6 Dec 2006 16:46:24 -0800, Josh Carroll wrote > > >> ** Port marked as IGNORE: multimedia/win32-codecs: > > >> is forbidden: Remote code execution: > > >> http://vuxml.FreeBSD.org/24f6b1eb-43d5-11db-81e1-000e0c2e438a.html > > >> > > >> Isn't this behaviour flawed ?? Or am I missing something ? > > You need to make config in /usr/ports/multimedia/win32-codecs, and > unselect quicktime. Then the port should install. This is assuming, > of course, that you can live without the QT codec(s). > > Josh OK, I will try it.. Thank you all. But the question remains -- if new port version is not vulnerable why i cannot upgrade to it ?? Cheers, Martin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade refusin to upgrade a port .. when it shouldn't imho
mato wrote: > On Wed, 6 Dec 2006 16:46:24 -0800, Josh Carroll wrote > ** Port marked as IGNORE: multimedia/win32-codecs: > is forbidden: Remote code execution: > http://vuxml.FreeBSD.org/24f6b1eb-43d5-11db-81e1-000e0c2e438a.html > > Isn't this behaviour flawed ?? Or am I missing something ? >> You need to make config in /usr/ports/multimedia/win32-codecs, and >> unselect quicktime. Then the port should install. This is assuming, >> of course, that you can live without the QT codec(s). >> >> Josh > > > OK, I will try it.. Thank you all. > > But the question remains -- if new port version is not vulnerable why i cannot > upgrade to it ?? > Its only not vulnerable if you unselect the quicktime codec. the vulnerability is in the quicktime codec. The port will by default use the stored config in /var/db/ports/win32-codecs/options and if this says to use the quicktime codec then it will not upgrade. This seems pretty sensible to me. Vince > Cheers, > > Martin > ___ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[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: portupgrade refusin to upgrade a port .. when it shouldn't imho
On Thu, 07 Dec 2006 13:46:18 +, Vince wrote > mato wrote: > > On Wed, 6 Dec 2006 16:46:24 -0800, Josh Carroll wrote > > ** Port marked as IGNORE: multimedia/win32-codecs: > > is forbidden: Remote code execution: > > http://vuxml.FreeBSD.org/24f6b1eb-43d5-11db-81e1-000e0c2e438a.html > > > > Isn't this behaviour flawed ?? Or am I missing something ? > >> You need to make config in /usr/ports/multimedia/win32-codecs, and > >> unselect quicktime. Then the port should install. This is assuming, > >> of course, that you can live without the QT codec(s). > >> > >> Josh > > > > > > OK, I will try it.. Thank you all. > > > > But the question remains -- if new port version is not vulnerable why i > > cannot > > upgrade to it ?? > > > Its only not vulnerable if you unselect the quicktime codec. the > vulnerability is in the quicktime codec. > > The port will by default use the stored config in > /var/db/ports/win32-codecs/options and if this says to use the quicktime > codec then it will not upgrade. This seems pretty sensible to me. > > Vince > I cannot access and check the port's Makefile right now ... Is it Makefile which says (conditionally) "hey i'm vulnerable" or is it portaudit/VuXML database which says that. I guess the former, otherwise freshports.org should mark the port as vulnerable. Right? Cheers, Martin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade refusin to upgrade a port .. when it shouldn't imho
mato wrote: > On Thu, 07 Dec 2006 13:46:18 +, Vince wrote >> mato wrote: >>> On Wed, 6 Dec 2006 16:46:24 -0800, Josh Carroll wrote >>> ** Port marked as IGNORE: multimedia/win32-codecs: >>> is forbidden: Remote code execution: >>> http://vuxml.FreeBSD.org/24f6b1eb-43d5-11db-81e1-000e0c2e438a.html >>> >>> Isn't this behaviour flawed ?? Or am I missing something ? You need to make config in /usr/ports/multimedia/win32-codecs, and unselect quicktime. Then the port should install. This is assuming, of course, that you can live without the QT codec(s). Josh >>> >>> OK, I will try it.. Thank you all. >>> >>> But the question remains -- if new port version is not vulnerable why i >>> cannot >>> upgrade to it ?? >>> >> Its only not vulnerable if you unselect the quicktime codec. the >> vulnerability is in the quicktime codec. >> >> The port will by default use the stored config in >> /var/db/ports/win32-codecs/options and if this says to use the quicktime >> codec then it will not upgrade. This seems pretty sensible to me. >> >> Vince >> > > > I cannot access and check the port's Makefile right now ... Is it Makefile > which says (conditionally) "hey i'm vulnerable" or is it portaudit/VuXML > database which says that. I guess the former, otherwise freshports.org should > mark the port as vulnerable. Right? In general, this sort of security flagging is done via portaudit's own database which is derived mostly from VuXML. To get around the lockout imposed by portaudit you can do: make DISABLE_VULNERABILITIES=yes but a) this doesn't disable any actual vulnerabilities, just the checking for their presence, and b) on your own head be it. Now, in the case of the win32-codecs port, it is done differently. The port Makefile says this: .if defined(WITH_QUICKTIME) FORBIDDEN= Remote code execution: http://vuxml.FreeBSD.org/24f6b1eb-43d5-11 db-81e1-000e0c2e438a.html ADDITIONAL_CODECS_DISTFILES+= qt63dlls-20050115.tar.bz2 \ qtextras-20041107.tar.bz2 PLIST_SUB+= QUICKTIME="" .else PLIST_SUB+= QUICKTIME="@comment " .endif ie. selecting the Quicktime plugins in the OPTIONS dialog, which causes WITH_QUICKTIME to be defined, means that the port will be marked forbidden, and any attempt to install it will be blocked. A simple 'make config' and unchecking that option will let you install the port with all of the other codecs. Freshports parses the VuXML database to mark ports as vulnerable -- the VuXML data contains a listing of the vulnerable package names and ranges of version numbers. VuXML doesn't actually have a way of distinguishing what options are enabled for the port, although the textual note in the entry explains the situation fairly clearly. It doesn't say "Users are advised to reinstall the port with the Quicktime support turned off" which might be a nice addition. The system will however prompt users to upgrade to a version of the port after the code to forbid installation with Quicktime stuff enabled was added. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. Flat 3 7 Priory Courtyard PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate Kent, CT11 9PW, UK signature.asc Description: OpenPGP digital signature
Re: cups-pstoraster vs. ghostscript 8.15
On Thu, 2006-12-07 at 12:45 +0300, Andrew Pantyukhin wrote: > It looks like both ports install some similar > files into share/ghostscript/8.15, in particular > share/ghostscript/8.15/lib/gs_init.ps. > > Frank, could you please look at it or should I > mark the two ports as conflicting right away? Mark them as conflicting for now. Probably the right thing to do would be to force cups-pstoraster to install its files in someplace like share/espgs/... but that'll take a bit of investigation. I didn't run into this since I use ghostscript-afpl rather than -gnu. Hmm, maybe mention that as an alternative on the CONFLICTS message? Or is that possible? -- Frank Mayhar [EMAIL PROTECTED] http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Firefox & thunderbird crash saving a file
I have had this problem since the update to the gnome 2.16 libs. I have had problems with firefox, thunderbird and eclipse crashing. On thunderbird this seems to happen most to me when attaching files from the file directory browser window. ganael.laplanche wrote: On Thu, 7 Dec 2006 09:10:05 +, James Seward wrote On 12/7/06, Mark Ovens [1]<[EMAIL PROTECTED]> wrote: I also had this behaviour on 6.2-PRERELEASE. Exactly the same bug at home on a 6.2-PRERELEASE :/ Ganaël LAPLANCHE [EMAIL PROTECTED] [3]http://www.martymac.com ___ [EMAIL PROTECTED] mailing list [5]http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [6]"[EMAIL PROTECTED]" References 1. 3D"mailto:[EMAIL PROTECTED]" 2. 3D"mailto:[EMAIL PROTECTED] 3. 3D"http://www.martymac.com"/ 4. 3D"mailto:[EMAIL PROTECTED] 5. 3D"http://lists.freebsd.org/mailm 6. file://localhost/tmp/3D___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Firefox & thunderbird crash saving a file
Guys, more of 'me too' are so useless. Please make your bug report useful. marcus is still waiting for someone to fill out his request[1]. I can't fill out his request, because I still can't reproduce it on two systems. If I can reproduce it then his request will be complete, because all of my ports are always compile with the debug. [1] http://lists.freebsd.org/pipermail/freebsd-gnome/2006-November/016179.html Cheers, Mezz -- [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: portupgrade refusin to upgrade a port .. when it shouldn't imho
Matthew Seaman wrote: > mato wrote: > >> On Thu, 07 Dec 2006 13:46:18 +, Vince wrote >> >>> mato wrote: >>> On Wed, 6 Dec 2006 16:46:24 -0800, Josh Carroll wrote ** Port marked as IGNORE: multimedia/win32-codecs: is forbidden: Remote code execution: http://vuxml.FreeBSD.org/24f6b1eb-43d5-11db-81e1-000e0c2e438a.html Isn't this behaviour flawed ?? Or am I missing something ? > You need to make config in /usr/ports/multimedia/win32-codecs, and > unselect quicktime. Then the port should install. This is assuming, > of course, that you can live without the QT codec(s). > > Josh > OK, I will try it.. Thank you all. But the question remains -- if new port version is not vulnerable why i cannot upgrade to it ?? >>> Its only not vulnerable if you unselect the quicktime codec. the >>> vulnerability is in the quicktime codec. >>> >>> The port will by default use the stored config in >>> /var/db/ports/win32-codecs/options and if this says to use the quicktime >>> codec then it will not upgrade. This seems pretty sensible to me. >>> >>> Vince >>> >>> >> I cannot access and check the port's Makefile right now ... Is it Makefile >> which says (conditionally) "hey i'm vulnerable" or is it portaudit/VuXML >> database which says that. I guess the former, otherwise freshports.org >> should >> mark the port as vulnerable. Right? >> > > In general, this sort of security flagging is done via portaudit's own > database > which is derived mostly from VuXML. To get around the lockout imposed by > portaudit > you can do: > > make DISABLE_VULNERABILITIES=yes > > but a) this doesn't disable any actual vulnerabilities, just the checking > for their presence, and b) on your own head be it. > > Now, in the case of the win32-codecs port, it is done differently. The port > Makefile says this: > > .if defined(WITH_QUICKTIME) > FORBIDDEN= Remote code execution: > http://vuxml.FreeBSD.org/24f6b1eb-43d5-11 > db-81e1-000e0c2e438a.html > ADDITIONAL_CODECS_DISTFILES+= qt63dlls-20050115.tar.bz2 \ > qtextras-20041107.tar.bz2 > PLIST_SUB+= QUICKTIME="" > .else > PLIST_SUB+= QUICKTIME="@comment " > .endif > > ie. selecting the Quicktime plugins in the OPTIONS dialog, which causes > WITH_QUICKTIME to be defined, means that the port will be marked forbidden, > and any attempt to install it will be blocked. > > A simple 'make config' and unchecking that option will let you install > the port with all of the other codecs. > > Freshports parses the VuXML database to mark ports as vulnerable -- the VuXML > data contains a listing of the vulnerable package names and ranges of version > numbers. VuXML doesn't actually have a way of distinguishing what options are > enabled for the port, although the textual note in the entry explains the > situation > fairly clearly. It doesn't say "Users are advised to reinstall the port with > the > Quicktime support turned off" which might be a nice addition. The system will > however prompt users to upgrade to a version of the port after the code to > forbid installation with Quicktime stuff enabled was added. > > Cheers, > > Matthew > > Matthew, that is a great answer!! Thank you! :-) The last question would be how to make make(1) /portupgrade/portsystem to ignore FORBIDDEN. Anyway, thanks again. Martin ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: [OT] Trying to build some software....
On 12/07/06 00:14, Sam Lawrance wrote: On 07/12/2006, at 4:02 PM, Eric Schuele wrote: Hello, Off topic? Maybe. I'm trying to build some software that has a port... yet the code I'm attempting to build is a *later* cvs snapshot. I'm trying to build it using the instructions on the originators website, not by using the port. When I run ./autogen.sh... it ends with the following: checking for zlib.h... yes checking jpeglib.h usability... no checking jpeglib.h presence... no checking for jpeglib.h... no configure: error: "Cannot find jpeglib.h. Make sure your CFLAGS environment variable contains include lines for the location of this file" I *do* have jpeglib.h in /usr/local/include, yet modifying CFLAGS has no effect. Nor does modifying CPPFLAGS (as the port does, I think). Take a look in config.log. Find out the command it's running to check for jpeglib.h - once you know what it's doing, you can try to fix it. Thanks for the response. ok... figured it out. heh.. I kept manipulating variables in make.conf. :/ make is not being used at this point. oops. Thanks again! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Regards, Eric ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: distfile belongs to?
On Tue, Dec 05, 2006 at 08:40:49PM -0500, Wesley Shields wrote: > On Tue, Dec 05, 2006 at 05:08:45PM -0800, Ade Lovett wrote: > > > > On Dec 05, 2006, at 13:59 , Doug Barton wrote: > > > > >Wesley Shields wrote: > > >>>@comment DISTFILE:$filename:$size:$md5:$sha256 > > > > > >I think that's good, the other information might come in handy down > > >the road. One thing you might want to consider is to put the md5 sum > > >at the end, since at some point down the road (maybe years from now, > > >but still ...) we're likely to drop md5 altogether. > > > > Better still would be: > > > > @comment DISTFILE:[':' =]* > > > > eg: DISTFILE:foo:SIZE=1234:MD5=...:SHA256=... > > > > Relying on the specific position of an item in a delimited list > > almost always comes back and bites in painful spots later on down the > > way. Minimal extra parsing required by consumers, and bits and > > pieces can be added/removed almost at will. > > > > -aDe > > I agree. I'll modify Doug's latest patch to add this. I've reworked the two patches to take all of the suggestions in. Part 1 (the pkg_info piece): - Silently ignores the -F flag when distfile information is not recorded in +CONTENTS. - Prints the information out in a human readable format (still respects -q). Part 2 (the bsd.port.mk piece) is the patch posted by Doug with Ade's suggestions. The entire thing no longer requires a change to pkg_create in order to function. Anymore thoughts/comments/ideas before I send-pr these? http://www.atarininja.org/~wxs/patches/package-distinfo-part1.diff http://www.atarininja.org/~wxs/patches/package-distinfo-part2.diff -- WXS ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: portupgrade refusin to upgrade a port .. when it shouldn't imho
On Thu, Dec 07, 2006 at 06:16:18PM +0100, mato wrote: > > Matthew, that is a great answer!! > Thank you! :-) > > The last question would be how to make make(1) /portupgrade/portsystem > to ignore FORBIDDEN. > "make -DNO_IGNORE" will get around this. But bypassing FORBIDDEN is generally not wise. -- Shaun Amott // PGP: 0x6B387A9A "A foolish consistency is the hobgoblin of little minds." - Ralph Waldo Emerson pgpXROdxFfA0O.pgp Description: PGP signature
Re: FreeBSD ports: 1 unfetchable distfile: sysutils/memtest
On 2006-12-07 10:05 +, "Bill \"distfiles\" Fenner" <[EMAIL PROTECTED]> wrote: # Dear [EMAIL PROTECTED], # # You are listed as the FreeBSD port maintainer for 1 port # whose distfiles are not fetchable from their MASTER_SITES. Could # you please visit # # http://people.freebsd.org/~fenner/portsurvey/[EMAIL PROTECTED] # # and correct the problems listed there? The individual port with # a problem is sysutils/memtest. It looks like a new version came out and the software author deleted the old version. I've submitted a PR to update the port to the latest version and added a mirror. Thanks -- Linh Pham [EMAIL PROTECTED] http://closedsrc.org/ pgpAjebaCfdiR.pgp Description: PGP signature
FreeBSD Port: trac-0.10.2
We are running into a fairly annoying bug in trac 0.10.2 that has been fixed in 0.10-stable. Would it be possible for the port to be upgraded to include these patches? Our issues are with ticket #4132. They can be seen here: http://trac.edgewall.org/milestone/0.10.3 Thank you, Doug Penny ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: distfile belongs to?
Wesley Shields wrote:
> Part 2 (the bsd.port.mk piece) is the patch posted by Doug with Ade's
> suggestions.
You missed the second patch I sent with the ${file%:*} changes. I've
attached a modified version of that patch which incorporates Ade's
change.
I plan to start adding the DISTFILE string to +CONTENTS files in
portmaster until it's supported in bsd.port.mk, so if anyone has a
comment on the format, please speak up now.
> The entire thing no longer requires a change to pkg_create in order to
> function.
Cool!
Thanks again for taking this on,
Doug
--
This .signature sanitized for your protection
Index: bsd.port.mk
===
RCS file: /usr/local/ncvs/ports/Mk/bsd.port.mk,v
retrieving revision 1.544
diff -u -r1.544 bsd.port.mk
--- bsd.port.mk 30 Sep 2006 19:25:45 - 1.544
+++ bsd.port.mk 5 Dec 2006 22:16:53 -
@@ -5395,11 +5395,20 @@
# files exist.
.if !target(generate-plist)
+.if defined(DIST_SUBDIR)
+PDS= ${DIST_SUBDIR}/
+.endif
generate-plist:
@${ECHO_MSG} "===> Generating temporary packing list"
@${MKDIR} `${DIRNAME} ${TMPPLIST}`
@if [ ! -f ${DESCR} ]; then ${ECHO_CMD} "** Missing pkg-descr for
${PKGNAME}."; exit 1; fi
@>${TMPPLIST}
+ @for file in ${DISTFILES} ${PATCHFILES}; do \
+ distsize=`${GREP} "^SIZE (${PDS}$${file%:*})" ${MD5_FILE} |
${CUT} -f4 -d' '`; \
+ distsha256=`${GREP} "^SHA256 (${PDS}$${file%:*})" ${MD5_FILE} |
${CUT} -f4 -d' '`; \
+ distmd5=`${GREP} "^MD5 (${PDS}$${file%:*})" ${MD5_FILE} |
${CUT} -f4 -d' '`; \
+ ${ECHO_CMD} "@comment
DISTFILE:${PDS}$${file%:*}:SIZE=$${distsize}:SHA256=$${distsha256}:MD5=$${distmd5}"
>> ${TMPPLIST}; \
+ done
@for file in ${PLIST_FILES}; do \
${ECHO_CMD} $${file} | ${SED} ${PLIST_SUB:S/$/!g/:S/^/ -e
s!%%/:S/=/%%!/} >> ${TMPPLIST}; \
done
signature.asc
Description: OpenPGP digital signature
Re: [CFR] ftp/curl update and API incompatibility
On Wed, 6 Dec 2006 14:56:57 +0200 Peter Pentchev <[EMAIL PROTECTED]> mentioned: > > x11/ecore > - Fix the packing list for the !x11 case. > Thanks for fixing the pkg-plist;-) Stupid error. -- Stanislav Sedov http://people.freebsd.org/~stas/stas.key.asc pgpJjNJ8ta4q3.pgp Description: PGP signature
FreeBSD Port: bogofilter-1.0.3
Hello, was released the stable version 1.1.1 some months ago. When you are going t o update the port? Bye, Giovanni pgp8ABOeS1e5y.pgp Description: PGP signature
Re: [CFR] ftp/curl update and API incompatibility
On Wed, Dec 06, 2006 at 02:56:57PM +0200, Peter Pentchev wrote: > - Not sure how to proceed with the PORTREVISION here, and also in > www/pecl-pecl_http - it seems that it is not customary for a PHP extension > to have a different PORTREVISION from the main port? Patch for pecl-pecl_http looks ok. Also, you may bump PORTREVISION in pecl ports also. Thank you for your efforts. -- Alexander Zhuravlev ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: distfile belongs to?
Doug Barton wrote:
> Wesley Shields wrote:
>
>> Part 2 (the bsd.port.mk piece) is the patch posted by Doug with Ade's
>> suggestions.
>
> You missed the second patch I sent with the ${file%:*} changes.
One more for fun. :) I was looking through bsd.port.mk for another
purpose tonight and came across ${ALLFILES}. Not only does it combine
dist and patch files into one variable, it has the benefit of not
adding the : stuff to the filenames in the first place.
Learning as I go,
Doug
Index: bsd.port.mk
===
RCS file: /usr/local/ncvs/ports/Mk/bsd.port.mk,v
retrieving revision 1.544
diff -u -r1.544 bsd.port.mk
--- bsd.port.mk 30 Sep 2006 19:25:45 - 1.544
+++ bsd.port.mk 8 Dec 2006 06:11:25 -
@@ -5395,11 +5395,20 @@
# files exist.
.if !target(generate-plist)
+.if defined(DIST_SUBDIR)
+PDS= ${DIST_SUBDIR}/
+.endif
generate-plist:
@${ECHO_MSG} "===> Generating temporary packing list"
@${MKDIR} `${DIRNAME} ${TMPPLIST}`
@if [ ! -f ${DESCR} ]; then ${ECHO_CMD} "** Missing pkg-descr for
${PKGNAME}."; exit 1; fi
@>${TMPPLIST}
+ @for file in ${ALLFILES}; do \
+ distsize=`${GREP} "^SIZE (${PDS}$${file})" ${MD5_FILE} | ${CUT}
-f4 -d' '`; \
+ distsha256=`${GREP} "^SHA256 (${PDS}$${file})" ${MD5_FILE} |
${CUT} -f4 -d' '`; \
+ distmd5=`${GREP} "^MD5 (${PDS}$${file})" ${MD5_FILE} | ${CUT}
-f4 -d' '`; \
+ ${ECHO_CMD} "@comment
DISTFILE:${PDS}$${file}:SIZE=$${distsize}:SHA256=$${distsha256}:MD5=$${distmd5}"
>> ${TMPPLIST}; \
+ done
@for file in ${PLIST_FILES}; do \
${ECHO_CMD} $${file} | ${SED} ${PLIST_SUB:S/$/!g/:S/^/ -e
s!%%/:S/=/%%!/} >> ${TMPPLIST}; \
done
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
