Re: port_history - track port commit message comments
On 10/27/06, Christopher Boumenot <[EMAIL PROTECTED]> wrote: Every time I upgrade a port I am usually left wondering what changed. Some other projects maintain special package-specific ChangeLog files. Maybe VCS logs is not the best place for documentation, because it's not as easily accessible as a flat file would be. Moreover, I think porters don't document the hacks they have to employ - just because there's nowhere to do that. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
git not updating my modular xorg ports tree?
Hi, I created a modular xorg ports tree: # cd /usr # mv ports orig-ports # git clone http://git.xbsd.org/freebsd/ports.git # cd ports # git checkout xorg This worked, and git pull used to work, but now it stopped working: # cd /usr/ports # git pull > Fetching refs/heads/master from http://git.xbsd.org/freebsd/ports.git using > http > Fetching refs/heads/xorg from http://git.xbsd.org/freebsd/ports.git using http > * refs/heads/xorg: does not fast forward to branch 'xorg' of > http://git.xbsd.org/freebsd/ports; > not updating. I do get 'got large-hex-number' and 'walk large-hex-number' messages, but git doesn't update. I tried a second 'git checkout xorg' and 'git prune' in /usr/ports, but that didn't help either. The tree is clean, except from a symlink to distfiles -> ../orig-ports/distfiles Suggestions? Regards, Rene -- GPG fingerprint = E738 5471 D185 7013 0EE0 4FC8 3C1D 6F83 12E1 84F6 (subkeys.pgp.net) "It won't fit on the line." -- me, 2001 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Bugathon, yeah it's time again
Ok, heads up folks. Ports have been frozen for some weeks now, and it's only a matter of time before ice starts melting. So we're planning to hold the next bugathon next week end (well, in one week). Same server, same channel (#freebsd-bugbusters @ EFNET), you have one week to grab a list of PR and start working on them. WWW: http://wikitest.freebsd.org/Bugathons/November2006 Note: Since I still don't receive much feedback from src-committers, I expect it to be mainly ports-related. Obviously I may be wrong and there will probably a few src-committers coming, this channel is still a good place to discuss bugs. -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: This is a digitally signed message part
Re: Flash 9
On Wed, Oct 25, 2006 at 08:27:20AM +0200, Alex Dupre wrote: > I got Flash Player 9 for Linux working on FreeBSD *with* sound. Hmm, this works but the audio sync is at least as bad as Flash 7 if not worse. I'm surprised they actually put in hooks for other sound APIs; from the technical blogs it didn't sound like they were even considering it. I also tried compiling the sample flashsupport module (can be found at http://www.kaourantin.net/flashplayer/flashsupport.c) on a Debian box and copying the resulting binary over. The audio sync was better but stability was far worse -- random segmentation faults. Craig ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: port_history - track port commit message comments
On Fri, 27 Oct 2006 16:26:54 +0400 "Andrew Pantyukhin" <[EMAIL PROTECTED]> wrote: > On 10/27/06, Christopher Boumenot <[EMAIL PROTECTED]> wrote: > > Every time I upgrade a port I am usually left wondering what > > changed. > > Some other projects maintain special package-specific > ChangeLog files. Maybe VCS logs is not the best place > for documentation, because it's not as easily accessible > as a flat file would be. > > Moreover, I think porters don't document the hacks they > have to employ - just because there's nowhere to do that. You all might want to take a look at what I do in mail/dspam[-devel]/[Makefile|files/UPDATING] -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" It [being a Vulcan] means to adopt a philosophy, a way of life which is logical and beneficial. We cannot disregard that philosophy merely for personal gain, no matter how important that gain might -- Spock, "Journey to Babel", stardate 3842.4 signature.asc Description: PGP signature
Re: port_history - track port commit message comments
On 10/28/06, Ion-Mihai IOnut Tetcu <[EMAIL PROTECTED]> wrote: On Fri, 27 Oct 2006 16:26:54 +0400 "Andrew Pantyukhin" <[EMAIL PROTECTED]> wrote: > On 10/27/06, Christopher Boumenot <[EMAIL PROTECTED]> wrote: > > Every time I upgrade a port I am usually left wondering what > > changed. > > Some other projects maintain special package-specific > ChangeLog files. Maybe VCS logs is not the best place > for documentation, because it's not as easily accessible > as a flat file would be. > > Moreover, I think porters don't document the hacks they > have to employ - just because there's nowhere to do that. You all might want to take a look at what I do in mail/dspam[-devel]/[Makefile|files/UPDATING] Yes, the idea is very bright. There's no rush however, so let's look at how other people deal with it, among ports committers and outside, before we set any standards in stone. [Wow, man, dspam ports is sure a place to learn many things :-) Great job!] Thanks! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: port_history - track port commit message comments
On Sat, 28 Oct 2006 01:04:05 +0400 "Andrew Pantyukhin" <[EMAIL PROTECTED]> wrote: > On 10/28/06, Ion-Mihai IOnut Tetcu <[EMAIL PROTECTED]> wrote: > > On Fri, 27 Oct 2006 16:26:54 +0400 > > "Andrew Pantyukhin" <[EMAIL PROTECTED]> wrote: > > > > > On 10/27/06, Christopher Boumenot <[EMAIL PROTECTED]> wrote: > > > > Every time I upgrade a port I am usually left wondering what > > > > changed. > > > > > > Some other projects maintain special package-specific > > > ChangeLog files. Maybe VCS logs is not the best place > > > for documentation, because it's not as easily accessible > > > as a flat file would be. > > > > > > Moreover, I think porters don't document the hacks they > > > have to employ - just because there's nowhere to do that. > > > > You all might want to take a look at what I do in > > mail/dspam[-devel]/[Makefile|files/UPDATING] > > Yes, the idea is very bright. There's no rush however, so > let's look at how other people deal with it, among ports > committers and outside, before we set any standards in > stone. The biggest problem is that it requires [a lot of] work for the commiter/submitter. The problem with the OP's work is that some submitters/commiters think that the CVS commit message should document the _port_ changes while others think it should also document (or at least provide pointers) to the changes in the software itself (I fall in the second category). Since we don't have a standard for this, relaying only on the CVS logs might drive one into nasty problems. And yes, some standards, one way or the other, or somewhere in between, whatever, as long as we're all __consistent__ would be very useful. One would know what to expect and what not to expect o find out from reading the CVS logs or files/UPDATING or whatever. From my POV it would be very nice to be able to read everything important for a port update from inside our Ports Tree, w/out having to go to the WWW site, etc.. > [Wow, man, dspam ports is sure a place to learn many > things :-) Great job!] Thanks. I'm pretty sure I re-invented the wheel a few times there; but overall I consider it to be one of the most user-friendly ports we have. We could _optionally_ support that kind of UPDATING file in our framework; and we also could support the check-options-version. -- IOnut - Un^d^dregistered ;) FreeBSD "user" "Intellectual Property" is nowhere near as valuable as "Intellect" BOFH excuse #188: ..disk or the processor is on fire signature.asc Description: PGP signature
Re: Bugathon, yeah it's time again
On Friday 27 October 2006 12:13, Florent Thoumie wrote: > Ok, heads up folks. > > Ports have been frozen for some weeks now, and it's only a matter > of time before ice starts melting. So we're planning to hold the > next bugathon next week end (well, in one week). Same server, same > channel (#freebsd-bugbusters @ EFNET), you have one week to grab a > list of PR and start working on them. > > WWW: http://wikitest.freebsd.org/Bugathons/November2006 > > Note: Since I still don't receive much feedback from > src-committers, I expect it to be mainly ports-related. Obviously I > may be wrong and there will probably a few src-committers coming, > this channel is still a good place to discuss bugs. I submitted a flurry of PR's right before the freeze (about 20 of them) Most of them deal with updating the download sites/fixing fetch problems, a few of them are version bumps. Do I need to show up in IRC to get these looked at? -- Thanks, Josh Paetzel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bugathon, yeah it's time again
On Fri, 2006-10-27 at 16:32 -0500, Josh Paetzel wrote: > On Friday 27 October 2006 12:13, Florent Thoumie wrote: > > Ok, heads up folks. > > > > Ports have been frozen for some weeks now, and it's only a matter > > of time before ice starts melting. So we're planning to hold the > > next bugathon next week end (well, in one week). Same server, same > > channel (#freebsd-bugbusters @ EFNET), you have one week to grab a > > list of PR and start working on them. > > > > WWW: http://wikitest.freebsd.org/Bugathons/November2006 > > > > Note: Since I still don't receive much feedback from > > src-committers, I expect it to be mainly ports-related. Obviously I > > may be wrong and there will probably a few src-committers coming, > > this channel is still a good place to discuss bugs. > > I submitted a flurry of PR's right before the freeze (about 20 of > them) Most of them deal with updating the download sites/fixing > fetch problems, a few of them are version bumps. Do I need to show > up in IRC to get these looked at? Will be easier to harass a ports committer if you can talk to him directly on IRC :-) -- Florent Thoumie [EMAIL PROTECTED] FreeBSD Committer signature.asc Description: This is a digitally signed message part
FreeBSD Port: clamav-0.88.5
Dear FreeBSD teams, First of all I wish to thank you for providing such a magnificent system for free to the world. I am really VERY CONTENT with this operational system! This mail is about a possible bug in the package ClamAV. I tried it out on a test computer. But when running "clamscan -r /path/to/stuff", systematically the next message was returned: segmentation fault (core dumped) I have been googling for hours and hours, but did not find any solution to this problem. Am I doing something wrong or is this a bug? Before installation (from ports) I did a portsnap upgrade. After uname -a I get the following: FreeBSD kolibrie.jasmijn.nl 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May 7 04:32:43 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386 It is just the generic kernel on my test computer. Hope to hear from you! Best regards from Holland, Wiebe Pestman ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Bugathon, yeah it's time again
On Fri, Oct 27, 2006 at 06:13:36PM +0100, Florent Thoumie wrote: > Ok, heads up folks. > > Ports have been frozen for some weeks now, and it's only a matter of > time before ice starts melting. So we're planning to hold the next > bugathon next week end (well, in one week). Same server, same channel > (#freebsd-bugbusters @ EFNET), you have one week to grab a list of PR > and start working on them. > Althought the ports tree is frozen, we are still very interesting in getting fixes to current versions in the ports tree. Even within the restrictions of a freeze, there are plenty of problems to fix out there to be found at the usual places (portsmon/pointyhat). A lot of those have been ignored for some time as people are too busy with version upgrades and thus they could use some extra attention. I'll be out traveling to several conferences the upcoming weeks, but I'd really like to see some focus towards fixing errors instead of version upgrades or PR busting. Good luck! -erwin -- Erwin Lansing http://droso.org Security is like an onion. (o_ _o) It's made up of several layers \\\_\ /_///[EMAIL PROTECTED] And it makes you cry.<) (>[EMAIL PROTECTED] pgp7QkY9Ns5lv.pgp Description: PGP signature
Re: Bugathon, yeah it's time again
On Sat, Oct 28, 2006 at 01:00:03AM +0200, Erwin Lansing wrote: > On Fri, Oct 27, 2006 at 06:13:36PM +0100, Florent Thoumie wrote: > > Ok, heads up folks. > > > > Ports have been frozen for some weeks now, and it's only a matter of > > time before ice starts melting. So we're planning to hold the next > > bugathon next week end (well, in one week). Same server, same channel > > (#freebsd-bugbusters @ EFNET), you have one week to grab a list of PR > > and start working on them. > > > Althought the ports tree is frozen, we are still very interesting in > getting fixes to current versions in the ports tree. Even within the > restrictions of a freeze, there are plenty of problems to fix out there > to be found at the usual places (portsmon/pointyhat). A lot of those > have been ignored for some time as people are too busy with version > upgrades and thus they could use some extra attention. > > I'll be out traveling to several conferences the upcoming weeks, but I'd > really like to see some focus towards fixing errors instead of version > upgrades or PR busting. If we'd thought about it we probably could have really benefited from a freeze bugathon, where the aim is to only fix port errors. Something to remember for next freeze. Kris pgpz1vKbuy4pt.pgp Description: PGP signature
Alanya Dreams
[1]www.alanyadreams.com References 1. http://www.alanyadreams.com/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Versions distributed only as diffs?
So... I'm looking at porting a debian package whose source appears to be distributed as an older version plus a couple of diffs to bring the old source to the current stable version. The two diffs, uncompressed, are about 101KB. Should I add slightly-modified versions of these diffs as patches in the port's files directory, making a 104KB port? That seems awfully heavy. Or should I make distfiles of the original diffs, and write some Makefile magic in post-patch to apply them to the older source distfile? Is there a precedent for this? And while we're at it, what do I name this bugger? The original source was version "0.1.2.ds1" ... but the first diff brings this to "0.1.2.ds1-2", and the second to "0.1.2.ds1-2.1". Shall I just strip out the alpha, and convert the remaining non-numerics to periods? Or just call this "0.1.2", and bump PORTREVISION when ds1-2.2 comes out? Thanks. -- Paul Chvostek <[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: Versions distributed only as diffs?
On Sat, 28 Oct 2006, Paul Chvostek wrote: So... I'm looking at porting a debian package whose source appears to be distributed as an older version plus a couple of diffs to bring the old source to the current stable version. The two diffs, uncompressed, are about 101KB. Should I add slightly-modified versions of these diffs as patches in the port's files directory, making a 104KB port? That seems awfully heavy. Or should I make distfiles of the original diffs, and write some Makefile magic in post-patch to apply them to the older source distfile? Is there a precedent for this? editors/vim does the second with about 90 small patches. So yes, there's precedent. --Curtis -- Curtis Jewell [EMAIL PROTECTED] "Killed enough? ... Yes, Your Highness, I think we all have." --John Patrick Ryan (from 'The Sum Of All Fears', Tom Clancy) [I use Pine, which deliberately does not display colors and pictures in HTML mail] ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
giftext segfault patch
Hi, I was running a spam filtering rule which uses giftext in a perl module to process image spam. I could not proceed as I was getting coredump messages about giftext. Today I have read another howto on a different approach to the setup of the spam filtering, and there I have come across information about giftext (from libungif port) and they have a patch for the crash - http://users.own-hero.net/~decoder/fuzzyocr/giftext-segfault.patch This patch applies cleanly to libungif. I am not testing again to see of giftext would still crash. I am requesting that you take a look at the patch to see if it would help us in the port. I am running FreeBSD 6.2-PRE -Wash http://www.netmeister.org/news/learn2quote.html DISCLAIMER: See http://www.wananchi.com/bms/terms.php -- +==+ |\ _,,,---,,_ | Odhiambo Washington<[EMAIL PROTECTED]> Zzz /,`.-'`'-. ;-;;,_ | Wananchi Online Ltd. www.wananchi.com |,4- ) )-,_. ,\ ( `'-'| Tel: +254 20 313985-9 +254 20 313922 '---''(_/--' `-'\_) | GSM: +254 722 743223 +254 733 744121 +==+ For your penance, say five Hail Marys and one loud BLAH! ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
what to use as "global" switch to not build x11 based ports ?
Hi, a USENET posting of a user, looking for a global make variable to prevent building of x11 based software, caused me to look how to do it best with FreeBSD. Maybe he came from Gentoo Linux ;-) At the moment I only found the variable WITHOUT_X11. But its only for ports, that can be built optionally with and without X11 support. It doesn't hinder directly to built x11 stuff using ports collection. Would we have to invent new global make variables and a new logic in bsd.port.mk or is there a more easier way with existing knobs that I perhaps overlooked ? IMHO a global make variable NO_X11 or something like this would need to be added and some logic that then still allows to build ports, that optionally can be built without x11 support. So NO_X11 should automatically set WITHOUT_X11, so that approx 250 ports (that use WITHOUT_X11) still could be built. Andreas /// -- Andreas Klemm - Powered by FreeBSD 6 Need a magic printfilter today ? -> http://www.apsfilter.org/ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "[EMAIL PROTECTED]"
