Re: Removal of Portmanager
On Wed, Jan 16, 2013 at 01:51:39AM +, RW wrote: Reports are sent to ports@ every 2 weeks. And I wonder how many people read carefully through all 478 entries. And your suggestion is ... ? mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Packages not updating on FTP
The build farm is still offline awaiting the code to be updated to a point where it will pass a security review. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: FreeBSD ports you maintain which are out of date
On Sat, Mar 09, 2013 at 08:33:06PM +1030, Gavin McDonald wrote: I'm happy to take maintainership of this one. Done, thanks. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Proposal: do not show up the dialog(1) by default?
We should step back and define the problem. The problem IMHO is that we have optimized for users who wish to save the maximum space on their systems, at the expense of users who want to install and upgrade ports with the minimum fuss. IMHO we should do the opposite. I think the number of users that care about whether p5-Foo-Bar installs its examples is zero. And yet, those were the dialogs I was presented last night on installing a 9.0 system with the latest ports tree. This seems wrong. Surely we can figure out some global-settings-editor? And, if a value has been set by that tool, and a port's metavariables haven't changed, skip the configuration dialog? mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: gccmakedep fix - 20130619
On Wed, Jun 19, 2013 at 01:51:42AM +0200, Oliver Pinter wrote: 3) Is not it better to submit via PR (GNATS) rather than a mailing list? That's what PRs are for... Mail are faster than PR-s. If we all go down that route, it means less and less people will try to read all the traffic on ports@. Please, use the PR database for what's it's intended for. Thanks. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADS UP] switch default xorg version in 9.1 and later
On Wed, Jun 19, 2013 at 04:03:36AM -0700, Thomas Mueller wrote: Now I am a bit confused, should it be x...@freebsd.org or freebsd-...@freebsd.org, or is one an alias for the other? They are aliases. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: [HEADSUP] New mailing pkg-fallout
On Thu, Jul 18, 2013 at 10:04:52AM +0200, Erwin Lansing wrote: You bet it is! Know you know what portmgr has been spending its time on for all those years and why we keep sining the same old song about quality control and pre-commit (and not post-commit) testing ITYM singing :-) In any event, this may be a case where looking at the mailing list through another lens may be less painful: http://lists.freebsd.org/pipermail/freebsd-pkg-fallout/ mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: Status of portsmon
On Sun, Aug 04, 2013 at 09:14:32PM +0200, Marcin Wiśnicki wrote: But didn't it use to show last successful builds too ? Now it just says None which is not very helpful. No, it doesn't have that information, sorry. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
[HEADSUP] upcoming removal of remaining 4.X bits from bsd.port.mk
Since the time that the RELEASE_4_EOL tag was applied to the Ports Collection, much of the legacy support for 4.X has been removed from individual ports (e.g., special-case code for old header layouts, marking ports BROKEN, and removing the checks for the antique perl in base). At this point anyone still using 4.X should have already frozen their ports tree at that tag. My next checkin to bsd.port.mk will remove the remaining vestiges of 4.X support so that we can start to try to simplify the code there. If you are (for whatever reason) still running 4.X, you will _not_ want to track this change. Again, anyone still on 4.X should have stayed with the RELEASE_4_EOL tag and hand-merged any other changes that they absolutely have to have. As stated for the last year or so, 4.X served us well but it became impossible for our team to support 4 branches of the src base in the ports. Here's to the continued adoption and success of 6.2, and the great strides in performance being made in 7.0. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: exim doesn't build on 4.9 (minor error)
This is probably due to some piece of code that is special-case for 4.X being removed. More is on the way (see my headsup from ~12 hours ago). mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: exim doesn't build on 4.9 (minor error)
Hmm, I may have spoken too quickly, there is a report of this same problem on 6.2. Never mind my noise. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Why are package builds failing for editors/abiword-plugins?
On Fri, Mar 09, 2007 at 02:53:03PM -0800, Eric P. Scott wrote: i386 and amd64 builds are failing as though something were forcing USE_AUTOTOOLS=libtool:15 and bypassing the included libtool. What's the difference? There was a checkin that indeed did just that, to try to work around the objformat removal problem. It has since been backed out. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[REMINDER] how to get the best use out of GNATS
Recently the bugbusting team has been seeing a few cases where PRs are being submitted without a clear understanding of how best to do so. Although there is a document that references this*, please let me reiterate a few points: - Please only send one PR for a particular problem. The mail queue and spam filtering take ~10 minutes to run (more if your address is greylisted) so you will not see an immediate email reply or update on the website. Please wait a few hours before assuming that something has gone wrong; if you think it has, please email bugmeister@ and we will look at it. - Your email address has to have a valid reverse lookup to be accepted. If the machine you are submitting from does not have this, please acquire and use a free email account such as [EMAIL PROTECTED] - Your email address will be public (in the database). If you do not want this, please use a free email account. - If your email bounces, it is much less likely that someone is going to be able to contact you if they need futher information about your problem. - Please trim replies when following-up. The database already has a copy. - Please do not use HTML mail. The GNATS spam-filters are set up to assume that such mail is spam. They are almost always correct. - Do not use content-type/quoted-printable. This will merely scramble your patches into unusability. - Remember, your submissions are going into a database, so any email mangling is undesireable. - Submissions of more than 500k are quarantined as possible spam. If your patch (or traceback) are that large, please consider posting them somewhere on the web and just submitting a URL. - The category for all ports is 'ports', not 'www' if your port is 'www/foo', nor 'misc' if your port is 'misc/bar'. This affects the automated systems that assign and track PRs. - In fact, the 'misc' category is almost always wrong. Its only legitimate uses are for a few things such as build infrastructure and boot loader code. If your problem is with the base system, it is almost certainly either kern or bin (unless you think it is particular to a processor or motherboard, in which case it is i386/amd64/etc.). Thanks. Mark Linimon, for the bugbusting team *http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/article.html ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Openssh
On Wed, Mar 21, 2007 at 04:51:08PM -0400, Alfredo Perez wrote: Do I need to be the maintainer of Openssh to submit a PR with a diff? No. We will forward your PR to the maintainer. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Openssh
On Wed, Mar 21, 2007 at 08:15:37PM -0400, Alfredo Perez wrote: That is the thing, the port does not have a maintainer Well, it will stay in the queue until a ports committer takes an interest in it. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [www/p5-libapreq2] Broken ?
On Fri, Mar 23, 2007 at 03:32:33PM +0100, Alexandre Brooks wrote: I'm currently trying to install www/rt36 port, with apache22 and mod_perl2, but this requires me to build the perl5 interface to libapreq2 (www/p5-libapreq2). Only problem, it is broken. You should mail the maintainer ([EMAIL PROTECTED]) and ask him. I do know it has shown up as broken on the package build machines. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: optional dependencies
Until someone implements some kind of capabilities system, we're stuck doing a bunch of logic in Makefiles. One problem no one has come up with a good solution for is mixing packages (with standard prerequisites) with installed ports (with custom prerequisites). mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[HEADSUP] please avoid using send-pr for the moment
spamassassin has crashed on hub.freebsd.org, which means that all incoming email for GNATS is just winding up in the spam directory. I have processed all the queued followup mail, but I cannot resubmit new PRs until spamassassin is restarted. Please do not send duplicates if you have already gotten a bounce message; the messages are in the queue waiting to be hand-processed. I'll send an all-clear when the situation is resolved. Thanks for your patience. Mark Linimon for bugmeister@ ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [HEADSUP] please avoid using send-pr for the moment
It's now clear to send PRs again. It will take a little while to clear out the backlog. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Apology for multiple PR (112106, 112107, 112108) submissions...
On Wed, Apr 25, 2007 at 11:35:16AM +0530, Amarendra Godbole wrote: I then queried the database to see if the PR was submitted, but nothing turned up. It takes 5-10 minutes for the automated processes all to run to process the latest PRs before they will show up on the web page. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: HEADS UP: xorg upgrade plans
On Wed, May 02, 2007 at 11:36:03PM +0200, Gerald Pfeifer wrote: Does this freeze apply to the whole ports tree, or only (relatively directly) affected parts of the tree? The latter is basically most of the tree :-) mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: net/sixxs-heartbeatd is now obsolete?
So, is it time to mark it as obsolete and pull it from ports? Yep, sounds like. Just send-pr it and it will get assigned to the maintainer (or this list if it's maintained by [EMAIL PROTECTED]) mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question about fields in INDEX files
The output from each port's make describe is documented at the describe target in: http://www.freebsd.org/cgi/cvsweb.cgi/ports/Mk/bsd.port.mk This is changed to a different format (a historical bug, too late to fix now because of POLA) via make index from ports/Makefile by the following script (see the foreach block at the end): http://www.freebsd.org/cgi/cvsweb.cgi/ports/Tools/make_index I will send you portsmon's portsIndexUtils.py file that you can work from to figure out this mess. (I don't see any reason to post it to the list). mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: games/sauerbraten
On Tue, May 08, 2007 at 07:49:02AM +0200, [LoN]Kamikaze wrote: Submit a PR and request a maintainer timeout. This will take a long time, but it's the only way. long time = 2 weeks mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: games/sauerbraten
On Tue, May 08, 2007 at 10:23:43AM +0200, [LoN]Kamikaze wrote: The last time I requested a maintainer time out it was something like two months. I have been much more active in the last few months on enforcing the maintainer-timeouts. If you are having problems, please email portmgr@ directly. Thanks. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: games/sauerbraten
On Tue, May 08, 2007 at 11:58:43AM -0500, Sam Stein wrote: I've already submitted a pr with the update; before I read about the maintainer timeout; should I just wait it out a while, and if nothing happens, request one? Or do it right away? Just wait it out for a while. At the moment, we're in a freeze to import xorg7.2 (and test and retest the upgrade scripts), so nothing can happen in the next few days in any case. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: php 5.2.2
On Thu, May 10, 2007 at 10:48:30AM +1000, [EMAIL PROTECTED] wrote: The latest release of PHP is out (as at May 3) and I'm just wondering if there's a schedule for updating the port - this release corrects some not insignificant security vulnerabilities. We are in an unusual ports freeze to do the preliminary work to import the xorg7.2 release, so at the moment we are holding off on this. We are, however, aware of the issue. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: php5-session-5.2.1_3
On Thu, May 10, 2007 at 10:00:06AM +0200, [EMAIL PROTECTED] wrote: Do you know that PHP 5.2.1 has a Security Enhancements and Fixes in PHP 5.2.2 and PHP 4.4.7 as reported on www.php.net? When will be available the PHP 5.2.2 in the ports? Please go read the archives of this mailing list over the past 24 hours. Thanks. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports tree : Xorg-7.2 release freeze, ETA?
On Sat, May 19, 2007 at 01:51:02PM -0700, Garrett Cooper wrote: Wouldn't it be sufficient to force major component testers (in this case Xorg 7.2) to use periodic snapshots of the ports tree (possibly CVS branching), while allowing continued development in the ports tree? In this particular case ... no. It was just too sweeping of a change, considering the X11BASE move. Other projects (GNOME, KDE, ...) do exactly this. It's a tradeoff of how much time is spent the one way or the other. The staging process for the xorg update involved literally dozens of major regression-test runs, most of which were done before the freeze. Asking them to have been doing even more, given the usual rapid rate of change in the ports tree, would have resulted in the integration taking even longer. As it was, we were pushing severe burnout on the people working on this thankless task. (And I thank flz@ again, if I haven't done so in public already). I can't imagine what major project on the horizon would ever be this sweeping again. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmaster version of UPDATING:20070519 users of x11/xorg ?
On Mon, May 21, 2007 at 09:15:44AM +0200, Hans Lambermont wrote: Do you happen to have a portmaster version of UPDATING:20070519 users of x11/xorg ? I think he may have gone to sleep already, so I'll step in and answer for him that he is working on it and may have a patch shortly. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: tinderbox and bad system call
On Tue, May 22, 2007 at 02:20:43PM +0200, Dag-Erling Smørgrav wrote: Then you need to run a kernel that corresponds to the newest userland the tinderbox wants to run - or from a different perspective, configure the tinderbox to only run userlands as old as or older than your kernel. Yes, that's the general idea, and what pointyhat does. In any case, it's your problem, not FreeBSD's. As usual, factual but badly stated. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: More speed increases for make-ing ports
On Tue, May 22, 2007 at 05:34:32PM +0400, Andrew Pantyukhin wrote: A seemingly better way may be to make these system vars available in make by default. Doesn't help anyone who runs -RELEASE, so a non-starter. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/111224: [PATCH] security/pam_per_user conflicts with security/courier-authlib
Synopsis: [PATCH] security/pam_per_user conflicts with security/courier-authlib Responsible-Changed-From-To: freebsd-ports-freebsd-ports-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Thu May 24 11:15:30 UTC 2007 Responsible-Changed-Why: Fix assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=111224 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD Port: p5-Math-BigInt-1.83
On Thu, May 24, 2007 at 09:21:09AM -0400, Robert Huff wrote: I'm having the same issue. Investigating a little reveals the size as listed in distinfo as 190172 and the size of the downloaded tarball as ~7200. Generally mismatches like this are returning HTML pages instead of the desired binary. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: email addresses and spam
On Thu, May 24, 2007 at 12:02:39PM -0700, Walter Ian Kaye wrote: All right, who released my email address to spammers? The mailing lists are public and mirrored all over the world. It's too late for that address, sorry. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADSUP: default for ports/Makefile 'make update' is changing
If you use 'make update', the default method is going to become portsnap. Currently, if you do not define one of the Makevars PORTSNAP_UPDATE, SUP_UPDATE, or CVS_UPDATE first, the code just complains at you and does nothing. This is one less thing that has to be set by default by an administrator. More advanced users can still set SUP_UPDATE or CVS_UPDATE, but if none of these is set, portsnap is assumed. This deprecates PORTSNAP_UPDATE. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Looking for speed increases in make index
On Mon, May 28, 2007 at 12:15:28AM +0200, Michel Talon wrote: To gain some performance, a first idea would be to simplify bsd.ports.mk. I am convinced that a substantial part of the 4000 lines are historical crap which serve no useful purpose. 11272 of LOC in bsd.*.mk, but who's counting. There are tons of variables who have probably purely anecdotical interest. There are targets which could be happily suppressed. Please let us know which functionality you think is extra. You should use the individual port Makefiles as well as ports/Makefile to figure out what is unused. For extra credit, please include ports/Tools/portbuild/scripts so the build cluster will continue to work. Please don't think I am picking on you specifically; however, about every 6 months or so someone decides that the ports framework is too complicated without saying exactly what needs to be removed. Since I look at all the portmgr PRs as they come in, and participate in rejecting in some of the (by our determination) more marginal features, I can assure you that not every single new proposal makes it in there, nor has in the past. Every- thing that's in there is because there was some specific justification for it (at least at the time). Given that we had no install base, a significant rewrite would not be a burden, but that's not the case. Please note, I've agreed for several years that a great deal of the code could be factored out into some kind of C library for speed and reduction of code duplication. Some work is going towards that in the Summer of Code. But the hard part is making it work, in a backwards compatible fashion, and doing the exhaustive regression testing to prove that it solves more problems that it creates. (portmgr spends a _lot_ of time on regression testing, behind the scenes.) In summary, the ports infrastructure is really complicated because it's trying to deal with all kinds of constraints and conditions. I challenge anyone who thinks things can be removed to roll up their sleeves and make a good case for it. I'd be happy to have something easier to read. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: xorg modularity
On Mon, May 28, 2007 at 10:16:11AM +1000, Edwin Groothuis wrote: It has been discussed on IRC, and I'm pretty sure that flz@ has been thinking about it during his sweat-shop-job. My opinion is: let's do the upgrade to 7.2 and the new framework first, then see what can be done about OPTIONizing it. My own feeling that is if we had spent the time trying to futher divide it up, it would have taken more time for our long-suffering folks to get it into the tree. That said, there's a lot of the demo and developer junk that few people need. Maybe I can talk myself into graphing the dependencies this week, that might make it possible to visualize it. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
removing stale ports [was: Re: make index failed]
I can't build index after recent update of ports via portsnap: wait..astk-client-1.5.0.1_2: /usr/ports/shells/bash2 non-existent -- dependency list incomplete As a reminder to committers, when removing stale ports, you also have to check the _optional_ dependencies in port Makefiles (yes, this involves a grep over the entire 17k+ Makefiles). It's a complete PITA, but it's necessary, but often overlooked. I speak as one who has triggered this particular bomb before :-) mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD%20Port:%20wzdftpd-0.8.1_1
On Thu, Jun 07, 2007 at 06:16:38PM +0200, Daniel Stefan Haischt wrote: attached you will find an modified wzdftpd port. Included are just changed files. fwiw, if you're going to Cc: to the list, you may as well just file it as a PR and then it will be auto-assigned to novel. Postings to the list can get buried underneath the flood of other postings. (If you had just wanted to send it directly to novel@, that step would not have been neccessary). Also, what in the world mail client are you using? The escaping of the spaces is the type of thing that gives the PR database indigestion when trying to track followups. mcl ___ 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: emulators/klh10
On Sat, Jun 09, 2007 at 07:48:44AM +0200, [LoN]Kamikaze wrote: So you better file a PR to step back from maintainership, so that volunteers don't have to wait for a time out. Already taken care of. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Samba 3.0.25a still broken
On Sat, Jun 16, 2007 at 07:50:14AM -0500, Jack Stone wrote: You could simply edit the Makefile in the samba port and reset the version shown at the top to the old version. Then, delete distinfo Then 'make makesum' Then 'make install clean' If the old port still remains in your /usr/ports/distfiles then it should create a new distinfo file If you don't have the old port, then 'make makesum' should start downloading it, then do 'make install clean' There is a tool to do this automatically. See ports-mgmt/portdowngrade. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to get a list of all kernel modules
On Sun, Jun 17, 2007 at 12:15:16AM -0600, M. Warner Losh wrote: I want a list of all the ports in /usr/ports that install kernel modules. IIRC they're all in misc/. Let me see if I can come up with a quick list. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to get a list of all kernel modules
On Sun, Jun 17, 2007 at 12:42:01AM -0600, M. Warner Losh wrote: I'd kinda hoped there was a pseudo category that I could key off of. Kinda sounds like there should be. Here's my list so far: audio/aureal-kmod audio/emu10kx comms/hcfmdm comms/ixj comms/ltmdm comms/uticom comms/vpb-driver graphics/kix-kmod graphics/plasma-kmod misc/zaptel multimedia/pvr250 multimedia/pwcbsd net/acx100 net/ipw-firmware net/iwi-firmware net/ng_daphne net/nvnet net/p54u palm/uppc-kmod security/vncrypt sysutils/cd9660_unicode sysutils/est sysutils/fusefs-kmod sysutils/ipmi-kmod x11/nvidia-driver ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: temporally out of action
ok, good luck on getting caught up. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PR problem -file handling.. long files
On Thu, Jun 28, 2007 at 06:38:24AM -0700, David Southwell wrote: There is a difficulty when posting PR's when a large debug file is needed to be posted to the PR as an attachment. Do you mean, via the web form or via send-pr(1)? The latter has a limit of 500k, via the FreeBSD.org email system. If something is larger than that, I would prefer that the debug file simply be posted to the web and a URL included. If you can't host the file yourself, email [EMAIL PROTECTED] and we'll host it somewhere. This way the size of the database won't grow as much. Thanks. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ChartDirector
On Mon, Jul 02, 2007 at 12:34:20PM +0200, Tim Rijavec wrote: can you add this package for ChartDirector for php to FreeBSD ports? that can be found at http://www.freebsd.org/ports/master-index.html Please use send-pr to submit this so that it won't just get lost in the mailing list traffic. See: http://www.freebsd.org/doc/en_US.ISO8859-1/books/porters-handbook/index.html http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/index.html http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/index.html mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
recent updates to portsmon.freebsd.org
I have just updated portsmon to the most recent development code. Most of this code has to do with the ability to create dependency graphs of failed or broken ports, and is not yet totally automated; thus, it is not (yet) visible to users. Other code has to do with internal schema changes. The most user-visible change is the new ability to be able to show a page of ports that fail on only one build environment. For example: http://portsmon.freebsd.org/portsconcordanceforbuildenv.py?buildenv=i386-7-fullbuildenv2=i386-6-full will show you the list of ports that fail on i386 but only on -current, not on -stable. Please let me know if you experience any problems with the upgrade. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proposal for another category in INDEX: common_deps
On Fri, Jul 20, 2007 at 05:11:27PM +0200, Michel Talon wrote: The only relevant info for determining what to install or build previously is RUN_DEPENDS and BUILD_DEPENDS. Everything else is garbage. The pointyhat error logs would tend to indicate that this isn't correct. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Proposal for another category in INDEX: common_deps
On Fri, Jul 20, 2007 at 12:40:02PM -0700, [EMAIL PROTECTED] wrote: the INDEX files -- so many that I think that items common to both build_deps and run_deps should be isolated and put into a new category called 'common_deps': How will this benefit us? Doug Reduce amount of processed text. If you read the log I posted there are a large number of what I refer to as 'excess characters'. These are the duplicate characters in both BUILD_DEPENDS and RUN_DEPENDS. IMHO the change in file format (and resulting POLA problems) outweighs the benefits of the faster scan. I'd rather see us audit the ports and try to eliminate unneeded entries in each. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Overly restrictive checks in the make process
On Fri, Jul 20, 2007 at 08:58:55AM -0400, Bill Moran wrote: Why? Is there a legitimate reason why the fetch process refuses to download this? The intention of the logic is to warn a user, as soon as possible, that they are spending time on something that will wind up being IGNOREd if it is installed. There is no logic there to try to figure out later version of port; it simply looks for is IGNORE set? Since some downloads take a long time, this does not seem too unreasonable to me. If we moved the check later, the process of trying to install a port that would be IGNOREd would be: spend time fetching and checksumming it, and only then tell the user that they had wasted their time. I think the best we could do is add something analagous to how DISABLE_VULNERABILITIES factors into it, and allow foot-shooting only if demanded, but turn it off by default. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Overly restrictive checks in the make process
On Fri, Jul 20, 2007 at 04:07:49PM -0400, Bill Moran wrote: Even better would be for make to realize that it's only doing the fetching, and do it anyway. That still doesn't help with the problem of a user who starts a 10MB download that won't work on his architecture or OS release. The code is all the same. This is the aggravation we are trying to prevent. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: What to do when the person who takes responsibility for a PR goes non-responsive?
I assume that you've already emailed the person? If so, sending email to portmgr@ is the right way to go. We'll attempt to find out if the person is busy/on vacation/overloaded/etc. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports depending on FORBIDDEN ports
I'm actually doing a slight superset by looking at dependent ports of (ignore/broken/forbidden/failed) ports, now that I have updated the graph and can see it better. It sounds like people are already working on the misc/compat3x dependents. Most of these ports are antiques. IMHO sysutils/eject should be fixed; there is a PR for it already: 112754. We definitely need to find someone who will keep zope up to date. I have privately emailed both the maintainer and the submitter of the last N PRs. There are a few other Python ports marked NO_PACKAGE, and I have also emailed the maintainers. This affects about 80 packages. Fixing all of these would add over 100 packages to the pointyhat builds. Thanks for taking a look at all of these. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: x11-themes/kde-icons-icosx - PLEASE DON'T DELETE
In general the way we want to assign maintainership is in conjunction with a port update/fix. Please submit anything that you come up with via GNATS. Even if in the meantime the port gets deleted, it can easily be brought back from the Attic. Thanks for volunteering to help. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Regarding upgrading nsc ports
On Fri, Jul 27, 2007 at 12:39:51PM +0530, Alagarsamy A wrote: can you please update it to latest version 0.80 (http://nsc-gothix.sourceforge.net/) ? ports@ is the default maintainer. No update will happen until someone (you?) submits a PR for it. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: emacs 22 and info files
On Wed, Aug 01, 2007 at 03:17:24PM +0200, Mark Evenson wrote: Which I would do but the [FreeBSD Bugs database][1] seems to not be returning any matches to queries Seems to be working fine for me now. However, I've seen a 'no PRs found' page to be displayed sometimes, possibly due to some internal timeout. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Out of order line in /usr/ports/MOVED
On Sat, Aug 04, 2007 at 06:01:48PM -0700, Doug Barton wrote: The following line was placed first in the file, instead of in chronological order. Is there a reason that it needs to be first? This is a bug. Fixed. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
new reports added to portsmon
These reports deal with package failures, adding together all packages that are intentionally not made, packages that fail, and all the packages that depend on them. Initially I generated these as graphs via GraphViz. However, the resulting images are so large that they take minutes to display on a browser such as firefox. This is useless. Now I have added a version of the reports in list form. Just see the List of package failures (direct and indirect) by buildenv on the charts and graphs page: http://portsmon.freebsd.org/chartsandgraphs/index.html . Each package that was not built is listed in the left column; the center column gives the explanation; and the third column lists the ports, if any, that depend on the non-built package. If you are interested in helping to get the packages in better shape, I think you will find these reports of help. (I am continuing to work on them, so the format may change.) Note: these reports show the state of the packages as of the last full runs. Some errors may have been fixed in the meantime; you will need to check the commit logs. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Popularity contest
On Sun, Sep 02, 2007 at 01:50:36AM +0200, Nils Vogels wrote: Since a little while, Debian has been using a popularity contest, that sends anonymous usage details of various packages that Debian users have installed. See sysutils/bsdstats. It apparently has not yet been extended to ports/packages, although a category is shown for that on the homepage (http://www.bsdstats.org). mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[HEADSUP] bsd.perl.mk import coming soon
The refactoring that gabor has done to recreate bsd.perl.mk will be imported soon, along with the many ports that it simplifies. Due to the size of the patch, I expect there to be collisions that I will have to adjust as I go, so expect the tree to be broken briefly while I work through the checkin. The main feature of the change will be to allow USE_PERL5= 5.8.0+ (and similarly for USE_PERL5_RUN, USE_PERL5_BUILD, PERL_CONFIGURE and PERL_MODBUILD). As a side-effect, the remaining few stragglers that attempt to keep perl5.003 going will be dropped. (Other committers have also been removing that code). mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[headsup] latest changes to bsd.perl.mk, and regressions
This should fix the remaining perl-related problems that people were seeing, each related to ports that conditionally included perl. The only remaining regressions that I can't yet explain are the following: */fpc-* fail to compile due some kind of flag failure. (They work on my 6.2 machine here). lang/dylan does not seem to build reliably. */hs-* are refusing to install. Someone's going to need to help me out with these. Thanks. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: [HEADSUP] problems with the autoconf upgrade
On Sat, Oct 06, 2007 at 05:40:05PM +0200, Max Laier wrote: On Sunday 30 September 2007, Mark Linimon wrote: Despite the fact that this was tested on the cluster, this upgrade has failed. Please hold off upgrading your ports tree until we can figure out what the problem is. Thanks. Did I miss the all good now, or is this still the latest on the subject matter? If the latter, what can we do to help? It was fixed 24 hours later. The actual problem turned out to be the m4 upgrade, which was quickly backed out. Anyone still having problems with autoconf should contact me directly. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[HEADSUP] portsmon default ports environment switched to i386-7
(For those who are not familiar with the FreeBSD Ports Monitoring System, or portsmon, that I wrote and maintain, you'll find more information at portsmon.freebsd.org.) To get ready for the 7.0 release, I've switched its model of the default ports build environment from i386-6 to i386-7. This mainly affects the status metavariables of each port. (It's a current limitation that portsmon only models one build environment.) E.g., its reports of ports that are marked BROKEN (i.e. fail to build for some reason) is now based on the evaluation of their state on -7 rather than on -6. This applies to both the interactive pages, and the email that is sent out every 2 weeks to maintainers and the mailing lists. Some of our maintainers will be seeing these messages for the first time. Don't panic; in many cases the newly-marked ports are failing to build because of the import of gcc4.2 into the base system. (All of the ports that are failing on i386 and/or amd64 have already been marked). We still have time before the 7.0 release to fix these problems -- most have already been fixed over the past few months. For some outdated software, it may not be feasible to provide patches; if this is the case, we can specify that the port can only be built with an older version of gcc. However, this should be used as a last resort. But the preferable solution is to provide patches and then send them to the upstream maintainers (if any) so that they can be incorporated there. In addition to the pages that most people are familiar with, I am in the alpha stage of generating reports that show the state of ports across all build environments. Unfortunately, the results are not yet dynamically generated. I had hoped to have that ready before release. In the meantime, the static reports will have to do. - http://portsmon.freebsd.org/chartsandgraphs/package_comparison.html compares the state of the packages for each build environment. The bars in the chart are divided up into: - unrestricted packages built; - restricted packages (built, but not available for download); - build errors; - not tried due to BROKEN, IGNORE, or FORBIDDEN; - not tried due to NO_PACKAGE; - not tried, other (these are due to drift in the ports tree between the time it was checked out, and the time it finished); - not tried, because it was a dependent port of one of the 3 lines above; - missing. These are due to bugs in the algorithm. - Clicking on each bar in the above will take you to a page for a particular build environment with a pie chart for the above values, and a tabular representation. (Bug: the links on those pages do not go anywhere useful). Examples: http://portsmon.freebsd.org/chartsandgraphs/package_status.amd64-7.html http://portsmon.freebsd.org/chartsandgraphs/package_status.i386-7.html - You can also (for the first time) see a tabular list of all ports that fail to package -- for the union of all the reasons above. Examples: http://portsmon.freebsd.org/chartsandgraphs/package_failures_list.amd64-7.html http://portsmon.freebsd.org/chartsandgraphs/package_failures_list.i386-7.html Here you can see, for a given build environment, the packages that were not built; the reasons that they were not built; and all the ports that depend on them. Clicking on each link in the left column will take you to the overview page for that port. Fair warning: these charts are pretty large; you may need to shrink them down to browse them effectively. Further note: some of the ones I have just uploaded show the results of a few very important packages that failed (x11/kdelibs3; devel/imake; and graphics/ImageMagick), so the statistics look bad. However, I believe these ports have already been fixed. Again, these reports are in an alpha state, but they offer a way for people interested in seeing e.g. what the state of the amd64 packages will be for 7.0, and hopefully give them a chance to fix some of them before the release. Finally, you don't need to let me know about the specific bugs in these reports -- I'm well aware of them :-) mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[HEADSUP] last run of GNATS weekly reports was broken
When we upgraded the machine that hosts these reports, we missed some files, and the reports came out null. I am currently working on testing the corrected script. While I'm working on it, I'm going to make a few tweaks. Let me know if you see anything odd in the results. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: py-punjab
On Tue, Jul 04, 2006 at 05:27:55PM -0300, Márcio Luciano Donada wrote: Port py-punjab (ports/net-im/py-punjab) has been removid from ports collection? cvsweb does not report it having been in the Ports Collection, nor is there an entry in MOVED. There is a pending PR to create one, however: http://www.freebsd.org/cgi/query-pr.cgi?pr=94024 mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Question about ports builds
On Thu, Jul 06, 2006 at 09:58:54PM +0300, Ion-Mihai IOnut Tetcu wrote: Actually support for 4.x is gone already. We're only required to mark the ports broken or incorporate patches from the users. Of curse, we try to fix broken ports on 4-STABLE but that battle is going to be lost. The latest results from the battlefield are not encouraging. I just finished another i386-4 build. Here are the stats of # of packages that completed versus whether the build is still running or not, compared to the slightly more than 15,000 possible packages: i386-4 10,167 (complete) i386-5 13,064 (still in progress) i386-6 13,599 (complete) i386-7 13,412 (still in progress) For comparison, a complete run of amd64-6 recently produced 12171 packages, and this was with kdebase3 and docbook-xsl not having finished successfully, which would have added many more. (I may try to restart it). The burden of trying to keep everything working on 4 i386 branches, 3 amd64 branches, and 3 sparc64 branches is too high at this point, especially with the degree of drift in such things as header files and base compiler between -4 and -5. Of course, most of these things can be fixed given sufficient maintainer and committer interest, but at some point you have to conclude that you're in the realm of diminishing returns. (pedantic note: we also try to keep two branches of ia64 running, at a lower priority. Even those may be in better shape than i386-4, currently.) Further note: there may be a recent checkin affecting the linux_base ports which completely skews this result; I am investigating. However. there are 206 legitimate build errors on i386-4 now; that doesn't include any port already marked as BROKEN. That's quite high. Those interested in further research can check out a new statistics display at http://pointyhat.freebsd.org/errorlogs/packagestats.html. (Among other things it will prove that you should not trust me to do web design, but never mind that.) mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: fetching linux (was: Re: Question about ports builds)
On Fri, Jul 07, 2006 at 02:45:02AM +0400, Boris Samorodov wrote: I noticed a few days ago that the first site at FEDORA_CORE_SITES (limestone.uoregon.edu) is acting not reliable. Your logs says the same (most distributions were taken from the next site -- mirrors.kernel.org). I'd rather delete the first site from the list. Please send me a patch to either delete it, or move it down, and I'll review it and commit it. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports support for RELENG_4 (Was: Re: Question about ports builds)
On Thu, Jul 06, 2006 at 09:55:47PM -0700, Doug Barton wrote: I think you're right about that, and my preferred method of operation for the ports that I maintain has been to try and test on RELENG_4 whenever possible, but not let not testing stop me from updating a port that works on 7-current and 6-stable. That's exactly what we are currently asking of the maintainers, yes. What I've found is that in those rare cases where there is an intersection between a port that is broken on RELENG_4 and users that care about that, I'm notified fairly promptly. If not by users, I usually get a krismail to the same effect. :) Right. At the moment I'm the standin for krismail, but the large number of failures on i386-4 has given me a little pause. I have asked a few maintainers for their opinion on what may be some common problems. I am actively working on this issue right now. I hesitate to send the krismails for i386-4 until I understand a little more what's going on (and possibly rerun it if we fix some things.) I have already done krismails about *-6 over the last 2 weeks. All that said, I'd love to officially drop support for RELENG_4, but I think that until we drop support for RELENG_4 in the base, dropping support for the ports would break faith with our users. At the same time, I think that some bit rot at the edges (of the seldom-used ports) is natural, and not to be mourned. We've already kind of said that on the portmgr policies page :-) We're also going to try to keep bsd.*.mk working on RELENG_4 at least as long as the secteam support for the branch. Note, however, that that deadline is also upcoming: January 31, 2007, according to http://www.freebsd.org/security/index.html#adv. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: last build at pointyhat and linux-gtk errors
On Fri, Jul 07, 2006 at 11:02:20AM +0400, Boris Samorodov wrote: I searched error messages at the last build at pointyhat. Strange enough but the build for x11-toolkits/linux-gtk used rather old ports tree. Current version is 1.2.10_3 (I committed a patch at Tue Jun 27 12:35:33 2006 UTC). The build for the port started at Tue Jul 4 12:31:39 UTC 2006 and used version 1.2.10_3. It takes a week for a full build on i386, longer on the others. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Ports support for RELENG_4 (Was: Re: Question about ports builds)
On Thu, Jul 06, 2006 at 09:55:47PM -0700, Doug Barton wrote: The way you break those numbers down is interesting. On i386 there are 206 errors on -4, 277 on -5, 119 on -6, and 151 on -7. The key fact that I missed in my first reply to this is that the -5 run was killed because there was some problem with it trying to rebuild the certain ports over and over and over again. The run is not complete*, even so. The 277 number is completely artificial because of this; I expect the actual number to be in the 110-140 range. (I vaguely recall seeing the number from the previous, non-doomed, run, but I didn't save it off anywhere, and the bits are gone now.) There's been enough stuff going on in the past N days where this just completely slipped my mind. mcl * see that yellow vs. the green? yeah, I _said_ I wasn't a web design person you would want to hire. But the Y/N column is the key that drives the bgcolor. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: graphics/linux-dri on 4.11
On Fri, Jul 07, 2006 at 12:18:15PM -0500, Matt Sealey wrote: I guess this has been completely looked over since BSD tar got very clever about it. The worry is.. isn't 4.x totally obsolete, unsupported now, and therefore not worth coding that fix for? :D The policy is that we no longer require committers to make sure things work on 4.X before they commit. To the extent that people send patches, things will keep running. The security team support for RELENG_4 is currently scheduled to end on 20070131. After that point, ports support on 4 is going to be especially problematic; I am currently trying to determine _exactly_ how bad the bitrot on 4 is. It's worse than people think. Anyone running a desktop needs to be on 6.1 or RELENG_6 now, unless they are one of the few people affected by one of the bugs, or for some reason are staying on 5.5 for now. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: graphics/linux-dri on 4.11
On Fri, Jul 07, 2006 at 01:33:55PM -0500, Matt Sealey wrote: Well this is a kind of internal-to-ports thing that needs a small change, not really a fix linux-dri thing. It could happen with plenty of packages, so who deals with that? There is no individual who's on the hook for that, exactly. What happens if you try to add a dependency on archivers/libarchive and change tar to bsdtar? mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: graphics/linux-dri on 4.11
On Fri, Jul 07, 2006 at 01:49:51PM -0500, Matt Sealey wrote: Yeah wouldn't a solution be to have bsdtar have a PORT_REPLACES_BASE kind of thing? Or a use.tar like use.perl? Well, it would be, if we were going to continue to support base systems without bsdtar already in them :-) mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portsdb -Uu broken on AMD64 system
This has already been fixed. Please re-cvsup and try again. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portinstall breaks with -m -j 4
BTW, I apologize for this is not at all a portupgrade issue, but an issue of the ports system. It is an issue with individual ports -- actually not the port (e.g. Makefile framework, pkg-*) but the individual applications (IIUC). Well, at least the ports system itself should not be broken able to work with this. With larger ports I manage to reduce build times by 40% with distcc and a second machine. As far as I see it the number of ports breaking is rather low. Please feel free to suggest a framework (complete with regression test framework) where the infrastructure code can learn which ports are safe. I think it's going to be a harder problem than you think it is. Note that appears to work and can be shown to work under arbitrary build circumstances for all users are IMHO going to be two very different classes of problem -- and the latter will need to be solved before it can be used on the package-building cluster. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[HEADSUP] last call for ports maintainers with maintainer-timeouts
Over the past few months I've been tracking maintainer-timeouts in an attempt to figure out which maintainers no longer have the time or interest to work on FreeBSD ports. The list below is those folks who either did not respond to email as of Jun 9, 2006 (or I misplaced their replies). So this is last call; please mail to me off-list if you are one of these folks and wish to keep your ports, or you otherwise know that these folks are still active. Thanks. Mark Linimon for [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [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]
Re: maintainer timeout
All I see is the following update with the text update to version 9.3.7, approved by: maintainer timeout by danfe (there were no PRs with libticables in the Synopsis): http://www.freebsd.org/cgi/cvsweb.cgi/ports/comms/libticables/Makefile?rev=1.16content-type=text/x-cvsweb-markup danfe, any more details here? mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports tree tagging again
On Wed, Aug 16, 2006 at 01:28:36PM -0400, Kris Kennaway wrote: I think someone (kuriyama?) was in fact already doing this, so getting the project started would not involve much work. Yes, that was already set up, but does not appear to be active. I don't know if the link was supposed to be broadcast publicly but interested parties can contact me off-list. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports tree tagging again
On Fri, Aug 18, 2006 at 04:21:38PM +0400, Roman Bogorodskiy wrote: There are severe logistical problems: Ports are currently expected to build for at least 3 different src branches, with between 2 and 6 different architectures in each. Multiply this by over 15,000 ports and that process isn't going to work. And this ignores interactions Yeah, that's the problem we should find a solution for. Other than adding a lot more build machines and/or decreasing the number of ports, what do you have in mind? mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[headsup] portsmon upgrade in progress
Some of the work that I'm currently doing to add the status of packages to the portsmon reports has meant that I needed to push out some earlier changes. For the first time, this has involved a Flag Day involving one of the attribute names in the database. In _theory_ this should not affect anything, but if it does, please contact me off-list. Thanks. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: problem generating INDEX
On Tue, Sep 05, 2006 at 11:33:47AM -0400, Robert Huff wrote: You get evidence supporting the hypothesis I'm an idiot. Thanks. No problem, there are plenty of ways to shoot your feet off, I've spent the last few decades iterating over them. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
[HEADSUP] new portmgr recommendation about adding new ports
Here is the result of a discussion amongst the portmgr members during the past few weeks, in response to the large number of new ports added to the Ports Collection in the last few months. - Recently we've seen evidence of an increase in the number of ports that are submitted just because the software is there, and not out of any underlying need for the port to exist. When considering a new port, portmgr would like to ask you to please apply the following criterion: New ports should only be submitted by someone who is actually using the software and will continue to use the port to maintain the software. Adding a port of software that you do not personally use, or do not use within the FreeBSD ports collection (such as an xpi browser extension that you manage using firefox and not using the Ports Collection), is not a good tradeoff between adding functionality and adding complexity. Each additional port requires resources, both machine (from the package building system) and people (to inspect the results from the package building system). This is especially true when you consider that we, as a team, are all trying to keep ports buildable on on 4 different branches and 5 different architectures (with increasing interest in arm and powerpc). Past experience shows that these ports often quickly fall behind as new versions are released, and when build breakages occur, they do not get fixed. In some other cases, some of our contributors try to keep ports viable by fixes and updating long after their real usefulness has passed, and that time could be better spent on the more worthwhile ports. While no one is suggesting that we go the route some projects have with some kind of 'gateway' process for approving new ports, at some point the number of ports will simply be too great for our infrastructure (package building system, sending PRs via email). Some common sense should help to keep us from reaching that point. As a reminder, the Ports Collection already has 198 ports marked BROKEN*, and 4291 unmaintained ones. We really don't need to add to these numbers. To summarize, we simply can't support all the possible applications out on the Internet, so we need to use common sense to try to keep it down to a maintainable number. mcl (*: on i386-6; the numbers are higher on the other architectures, and -CURRENT) ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Help to maintain port Websieve 0.63a
On Thu, Sep 21, 2006 at 10:01:20AM +0200, Martin Schweizer wrote: How can I help to do this? How it the corresponding person (the maintainer is ports@). [EMAIL PROTECTED] is the string used to indicate that a port is not maintained by anyone; so until someone steps up and contributes (e.g. by sending in PRs to fix it) it will remain broken. A good place to get started learning about how to contribute can be found at http://www.freebsd.org/doc/en_US.ISO8859-1/articles/contributing-ports/ . mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: cvs commit: ports/databases/ruby-mysql Makefile
On Wed, Sep 20, 2006 at 09:27:21PM +0900, Akinori MUSHA wrote: http://pointyhat.freebsd.org/errorlogs/i386-7-latest/ruby18-mysql-2.7.1.log Note: Some of those logs may not exist depending on the timing. The previous errorlogs are always archived. If you have access to pointyhat, you can find them that way; otherwise, you'll need to do some detective work on the web pages under Archive / All error logs at http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/ . For instance, I find the ruby18-mysql log at e.4.20060713/ruby18-mysql-2.7.1.log.bz2 e.4.2006071303/ruby18-mysql-2.7.1.log.bz2 e.5-exp.2006091406/ruby18-mysql-2.7.1.log e.5.20060726/ruby18-mysql-2.7.1.log e.5.2006072607/ruby18-mysql-2.7.1.log e.6.2006091606/ruby18-mysql-2.7.1.log Note that to save space, older errorlogs are compressed. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Syncing up with the package build cluster
On Fri, Sep 22, 2006 at 04:21:15PM +0930, Daniel O'Connor wrote: Is there an easy way to find when the ports tree was checked out for a given package run? I have now added a link to the cvsdone file which already existed, to the page at http://pointyhat.freebsd.org/errorlogs/packagestats.html . Look under the column cvs date. Note that this date is a timestamp just _after_ the cvs update -d finished. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Port Bloat
On Sat, Oct 14, 2006 at 10:53:32PM -0700, Peter Thoenen wrote: B) In line with A, has anybody thought about just marking ALL [EMAIL PROTECTED] as scheduled for deletion on X date. It turns out that a few of them are key pieces of infrastructure. Perhaps we can generate a list of ports that we would really like to see adopted. It has also turned out, in the past, that one man's trash is another man's treasure as the old saying goes. When we first instituted the DEPRECATED/ EXPIRATION_DATE process, a lot of people did indeed adopt some ports in a flurry of activity, but there was a fair amount of fuss generated, too. Since then, several hundred stale/dead ports have indeed been pruned. Unfortunately we don't really have any good proxy for what ports are in use. The closest we have is FreshPorts subscriptions, which, the last we checked, showed that several thousand ports were not being tracked by anyone who subscribed. Unfortunately the sample space for FreshPorts is self-selecting so it can't be taken as authoritative. I advocate that people subscribe to FreshPorts and list the ports they use so that we can better judge this. One of my eventual goals for portsmon is to include date of last commit (as well as the fetch survey results) to try to generate another proxy for this. I don't have any other ideas that wouldn't just create a bunch of controversy, however. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: compat3x
On Wed, Oct 18, 2006 at 01:06:10PM -0600, Charlie Sorsby wrote: What does this mean and why is it so? Wednesday, 18 Oct, 2006 -- 12:59:41 MDT === compat3x-i386-4.4.20020925 is forbidden: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available. It means there is no feasible way to write a secure version of antique software and do the necessary regression testing to guarantee that it is so. While I can understand lack of support for old versions of the OS, I cannot understand nor can I fail to resent y'all's making its use impossible. It's not impossible. Comment out the line and install it, but understand that by doing so you now have a vulnerable system. Perhaps if y'all were not so intent upon making freeBSD less and less BSD and more and more invented here such problems would be less common. BSD ran on VAXen and the like. FreeBSD runs on dual-core processors with power management, wireless networks, disks that were larger than the BSD designers thought possible via quantum physics (I have this first-hand), and gigabit networks; all on processor architectures that did not exist (in anything close to their current form) back in the halcyon days. So, we get it either way: if we attempt to bring in new features, we are criticized for trying to invent new solutions; if we attempt to stay where we are, we suddenly find we don't run on any hardware that anyone actually cares about anymore. Given this, we do our best to generate consensus about what most people are interested in working on and maintaining, and go from there. btw, we don't support Mosaic in the Ports Collection, either, for exactly the same reason. I removed it myself. It was a great piece of software for its time. That time passed. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/databases/postgresql81-server
On Mon, Oct 30, 2006 at 04:48:27PM -0600, Craig Boston wrote: Is fixing broken ports eligible for commiting during the freeze? Yes, with portmgr approval, of course. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/databases/postgresql81-server
On Mon, Oct 30, 2006 at 06:42:45PM -0600, Craig Boston wrote: Great, I'll file a PR later tonight unless somebody beats me to it. Well, we just lifted the freeze, so it's too late for 6.2, but it can go into the ports tree anyways. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to make minor changes
On Tue, Oct 31, 2006 at 12:04:34PM -0600, Paul Schmehl wrote: If I submit PRs for this, do I have to set PORTREVISION to 1? Or does it matter for such a minor change? Since it doesn't affect the package (install/deinstall), PORTREVISION should not be bumped. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ports/105220: maintainer update: audio/kid3
Synopsis: maintainer update: audio/kid3 Responsible-Changed-From-To: freebsd-ports-freebsd-ports-bugs Responsible-Changed-By: linimon Responsible-Changed-When: Mon Nov 6 19:49:36 UTC 2006 Responsible-Changed-Why: Canonicalize assignment. http://www.freebsd.org/cgi/query-pr.cgi?pr=105220 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Undefined reference to 'llrint' when portinstalling multimedia/mplayer
On Tue, Nov 28, 2006 at 11:52:49AM -0800, Jeremy Chadwick wrote:
Something like this should do just fine:
.if ${OSVERSION} 504000
BROKEN= Requires FreeBSD 5.4 or later, for llrint(3)
.endif
s/BROKEN/IGNORE/. BROKEN=doesn't currently work. IGNORE=known not to
work now, nor will it work later.
FYI.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Index build fails at audio/gstreamer-plugins-esound
On Sat, Dec 02, 2006 at 05:47:58PM -0500, John Abrams wrote: I'm trying to make index on a FreeBSD 4.11-STABLE box, and for some time I keep getting this error (I have cvsupped several times): You are seeing a side-effect from most of the ports maintainers and committers having moved to 6.X, especially for those working on desktop- oriented apps such as this. Is there a particular situation that is preventing you from upgrading? mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: failure of policy
On Mon, Dec 11, 2006 at 01:23:54PM -0500, Vivek Khera wrote: Reading this PR more closely it seems I was not even notified, as Oleg Gawriloff [EMAIL PROTECTED] is described as the maintainer and is the one responding to maintainer queries, which he is not. What isn't detected well is if someone who isn't the maintainer submits a PR with the 'maintainer-update' state. Edwin and I need to look at our respective codebases and figure out what happened in this situation. But you're right, this is not the way that it is supposed to work. Please accept my apologies, and we'll look at the code. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: failure of policy
But you're right, this is not the way that it is supposed to work. Please accept my apologies, and we'll look at the code. Well, this looks to have been a combination of two human errors (on that particular PR), which the code really doesn't know how to deal with. But after looking at it, I'm not too sure what we could have done differently. So please folks, let's be careful out there as the old US TV show said, and respect the maintainers' prerogatives. Thanks. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: How to construct this port?
I'll echo pav here. For people that don't want to answer questions or deal with reminder-email from portmgr, the best thing to do is turn the port over to [EMAIL PROTECTED] and just submit PRs for updates. That's the difference, in my view, between being a 'submitter' and being a 'maintainer'. We need both, of course. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Problems with PR system?
There seems to have been a temporary problem with the email system either involving spasassassin or NFS. The message is queued and I will rescue it tomorrow; I am simply too tired tonight. I will note, again, that these problems should always be forwarded to bugmeister@ rather than the public lists. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Regarding dns/djbdns
On Mon, Jan 08, 2007 at 02:28:54AM +0200, Cristian KLEIN wrote: I have contacted this e-mail address as this is what make maintainer gave me for dns/djbdns. [EMAIL PROTECTED] is the address that unmaintained ports are assigned to, so you may or may not get a response. If you wish, you can file a PR against it, although if no one is interested in the port, it may simply languish. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to [EMAIL PROTECTED]
status of FreeBSD packages [was: Re: pkgupgrade]
On Wed, Jan 31, 2007 at 05:19:33PM +0100, Michel Talon wrote:
In my experience the Debian system is far more reliable than the
FreeBSD one, but such reliability will never be accessible to FreeBSD
as long as *all* ports are not available as packages.
I have also been working on the 'packages problem' from the standpoint
of portsmon. The first approximation is to add the state of package
uploads (using ftp4 as a reference) to each individual overview page:
http://portsmon.freebsd.org/portoverview.py?category=audioportname=easytag-devel
Currently, the latest successful package builds on pointyhat are not
shown in the left side of the table at the bottom. I am considering
adding this.
You can also see the state of all the packages on all the FTP sites:
http://portsmon.freebsd.org/portsuploadstatus.py
I currently have an action item to contact the FTP site maintainers
for sites that are out of sync.
Also, you can see the state of the current package builds on pointyhat:
http://pointyhat.freebsd.org/errorlogs/packagestats.html
The 'skipped' column is the union of all the 'ignore' reasons.
In addition, I want to add tools that will show _why_ packages are not
built, and divide it up into {legal reason/marked 'ignore'/failed/dependent
on a package falling into one of the above}. The latter of those 4 is
what is shown in the 'missing' column when a package build is finished.
I also want to add tools to allow comparison of packages between two
different build environments.
Note that this code is still beta, and I am actively working on bugs.
I am hoping that this work will lead to better packages on FreeBSD.
mcl
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]
