Re: DNS Flag Day and freebsd.org problems
I have already forwarded the email to clusteradm@. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: php56
AFAIK you can either: - use packages and revert to 2018Q4; or - re-add the sources locally and compile them from source. IIUC those are your only two options. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
On Sun, Dec 16, 2018 at 08:21:14PM -0600, Justin Hibbits wrote: > You can try to build the broken ports either by deleting the BROKEN > line in the Makefile True, but see below ... > or through some poudriere trickery -T Try building BROKEN ports by defining TRYBROKEN for the build. (This is the equivalent of forcing an ignore of the BROKEN lines). Now, having said that ... over the past 2 weeks I've done a TRYBROKEN run over everything that is marked BROKEN on powerpc64. In the few cases where the port built, I deleted the line. So AFAIK all the ports marked BROKEN really don't build. I can provide logfiles to anyone who wants to do the debugging. Tangential to BROKEN is the makevar NOT_FOR/ONLY_FOR. This doesn't get overridden by TRYBROKEN. This setting is used to say "this port is not able to build on this architecture due to either missing code, lack of support for e.g. big-endian archs, and so forth." For those issues you may need to check with the port's upstream. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
If we are talking powerpc32 and not powerpc64 (as I assumed), the one developer continuing to actively work on it is jhibbits@. Perhaps he can give you a status report. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
On Sun, Dec 16, 2018 at 04:35:32PM -0500, Alex McKeever wrote: > I ran into problems compiling the CDE in FreeBSD 12.0 RC3 (PowerPC) > on my eMac. I don't know of anyone else who has tried to run it. The server-class ports on powerpc64 have been in good shape for several years. However, the desktop ports are lagging way behind. For instance, we are still working to get gnome and kde working properly. Other desktop environments are going to require more people to take up working on them. I personally would like to see powerpc64 ports at (near-) parity with amd64, but we have a lot of work to go yet. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Common Desktop Environment broken when compiling from ports tree on FreeBSD 12 RC3 (May also apply to the final build)
On Sun, Dec 16, 2018 at 06:12:35PM -0700, Alan Somers wrote: > As for powerpc on tier 1, I'm afraid that it's not likely to ever > happen. Powerpc is dying. If anybody were buying new ppc hardware, > then it would be a different story. But I predict that powerpc is > likely to be dropped than to go Tier 1. Sorry. Thank you for discouraging me and the other folks working on powerpc64. New systems with Power9 are being sold by a company called Raptor Systems in Round Rock, Texas. Several developers have them, and others (including me) have them on order. I have been working on bringing powerpc64 ports up to parity for quite some time. If you are not aware of the effort that myself, and many others, have been putting in, then you are obviously not reading the svnports@ list, and should not be speaking as an authority. src work on supporting P8 and P9 is also in very active development. Please try to keep up with the development situation for a plaform before posting about it. Frankly, I find your post insulting. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: What will be tier 1 for 12.0-Release?
On Wed, Oct 24, 2018 at 04:39:41PM +, Mark Linimon wrote: > uh ... those were probably the last ones I did. never mind, this is a new machine under test. I missed seeing the listing even when I looked at pkg.FreeBSD.org ... earlier today. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: What will be tier 1 for 12.0-Release?
> > Good to see that there are pkg builds for powerpc64 these > > days: FreeBSD:12:powerpc64 and FreeBSD:11:powerpc64 are > > listed in the Tier-2 support package sets list as well. uh ... those were probably the last ones I did. AFAIK no package building has been done at isc for years. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FCP-0101: Deprecating most 10/100 Ethernet drivers
On Wed, Oct 24, 2018 at 05:19:33AM -0700, Rodney W. Grimes wrote: > And I have read case law that boiled down to the presents vs absence > of a comma If we are now going to evaluate all proposed changes to FreeBSD on the same rigid principles as the US legal system, I'm done. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FCP-0101: Deprecating most 10/100 Ethernet drivers
On Thu, Oct 04, 2018 at 08:44:11AM +, Alexey Dokuchaev wrote: > OK I guess I can understand removing 10 (I personally haven't seen > one in a very long time) but 100 are omnipresent and most of my NICs > are in fact 100. Sigh. If you really plan to still be using i386 and 10/100 ether in 2024, perhaps you should consider NetBSD. You can buy used core i5 laptops for around $20 if you shop around. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: drm / drm2 removal in 12
On Sat, Aug 25, 2018 at 07:22:06PM -0700, Randy Bush wrote: > plonk Indeed. I encourage everyone else to do the same. I'm far too old for proof-by-repetition. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: drm / drm2 removal in 12
On Sat, Aug 25, 2018 at 07:07:24AM +0800, blubee blubeeme wrote: > Are these guys insane and please avoid the nonsense about you're doing this > in your spare time. Let us know how whatever OS you wind up using instead works for you. I suggest you look for one that will put up with your constant harangues. There are very few people on the mailing lists as nasty and rude as yourself. It is tiresome, demotivating, and childish. Please go elsewhere. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: portsmon.freebsd.org via freshports?
> Is portsmon ever coming back? Sometime in Q2, yes. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
package building performance (was: Re: FreeBSD on AMD Epyc boards)
On Wed, Feb 14, 2018 at 09:15:53AM +0100, Kurt Jaeger wrote: > On the plus side: 16+16 cores, on the minus: A low CPU tact of 2.2 GHz. > Would a box like this be better for a package build host instead of 4+4 cores > with 3.x GHz ? In my experience, "it depends". I think that above a certain number of cores, I/O will dominate. I _think_; I have never done any metrics on any of this. The dominant term of the equation is, as you might guess, RAM. Previous experience suggests that you need at least 2GB per build. By default, nbuilds is set equal to ncores. Less than 2GB-per and you're going to be unhappy. (It's true that for modern systems, where large amounts of RAM are standard, that this is probably no longer a concern.) Put it this way: with 4 cores and 16GB and netbooting (7GB of which was devoted to md(4)), I was having lots of problems on powerpc64. The same machine with 64GB gives me no problems. My guess is that after RAM, there is I/O, ncores, and speed. But I'm just speculating. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ABI changes within stable branch
On Tue, Sep 19, 2017 at 07:33:20PM -0600, Warner Losh wrote: > FreeBSD has always had a policy of backwards compatibility. By that > definition we are stable. What we don't promise is full forwards > compatibility, which is what you are asking for. In particular, "we add things to the ABI" sometimes changes the way packages build (e.g. if a config script auto-detects the change). Because of this, you have to be very particular that you are running either 11.0-built things, or 11.1-built things, but not a combination. If you're running 11.X-stable across the thing-added-to-ABI boundary, then you can get into the same bad state. Ports rarely get into that state across that boundary, and only a few of them, but it is very annoying when it does happen (e.g. rsync). The only way to make sure that doesn't happen is to cancel the developers' ability to modify the ABI in any way. Unfortunately, I don't see that happening. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ABI changes within stable branch
On Tue, Sep 19, 2017 at 10:15:32AM +0200, Kurt Jaeger wrote: > A pointer to the official policy would be nice 8-} 3rd paragraph of: http://www.freebsd.org/portmgr/policies_eol.html mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: pefs not working
On Thu, Jul 06, 2017 at 07:55:07PM -0500, Chris Watson wrote: > Pefs is in ports under security I believe. http://www.freshports.org/sysutils/pefs-kmod/ mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: FreeBSD 11.1-BETA3 Now Available
On Sat, Jun 24, 2017 at 09:18:26PM +, Thomas Mueller wrote: > excerpt from Glen Barber's announcement: > > > A list of changes since 11.1-RELEASE are available in the stable/11 > > release notes: probably meant 11.1-BETA2 ? mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Nightly disk-related panic since upgrade to 10.3
On Fri, Oct 21, 2016 at 10:14:26AM +0200, Andrea Venturoli wrote: > I've tried this way, but altough I'm quite proficient with [k]gdb I tend to > get lost in FreeBSD's kernel's source code, which, unfortunately, I'm not > familiar with. > > BTW, I had read that book years ago; I searched for it now, but a 2005 > edition still comes up. Has it ever been updated? My usual go-to documentation John Baldwin's paper: http://www.bsdcan.org/2008/schedule/attachments/45_article.pdf mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Benchmarks results for Compilers on FreeBSD 11
I'll demur just a bit on your points. On Mon, Aug 29, 2016 at 08:51:02PM -0700, K. Macy wrote: > "we need a compiler to build the system" (a prebuilt package does that > just fine), Well, yes, for a tier-1 machine; and one that is connected to the network. > I can't speak for the whole universe of users, but I think it's safe > to say that most users are not power users who individually configure > ports tailored to their needs. We've certainly tried to provide a migration path away from that, but I don't think anyone has statistics about how far along we are. IMHO we can't assume it's 100%, or maybe even 80%. > I think my experiences on Ubuntu [...] are illustrative. A number of years ago Ubuntu and FreeBSD had barely overlapping audiences: end-users and developers. With all the improvements to pkg and tier-1 packages I hope that is changing -- the goal of expanding the reach is why I supported all the changes I saw being made. But for me an attraction has always been "you can build it out of the box", even if I rarely do it (e.g. I am not working in the kernel/driver area), mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Benchmarks results for FreeBSD 11
On Mon, Aug 22, 2016 at 09:57:24AM +1000, Dewayne Geraghty wrote: > unless knowledgable people respond publicly and/or in the phoronix > forums [...] this interpretation of reality will be fixed in decision- > makers' minds and consequently the uptake (and support) of FreeBSD. IIRC this has been done before and hasn't really been productive. OTOH I don't recall the details. FreeBSD hasn't had a benchmarking guru since Kris Kennaway retired from working on FreeBSD. It would be really nice if Someone(TM) took up the position. I would have to educate myself on the whole topic, so I'm not a likely nominee. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Where is 10.2-STABLE?
On Wed, Mar 30, 2016 at 11:04:30PM -0700, Ronald F. Guilmette wrote: > I would however like to ask if there is an ETA for 10.3-RELEASE > actually being official and final. >From the front page of www.freebsd.org, click on the link "Upcoming: 10.3" which will take you to https://www.freebsd.org/releases/10.3R/schedule.html . That shows that _in theory_ the announcement should have been made on the 29th. I am not on the Release Engineering team so I can only go by the schedule. > Also, and separately, I should ask who would be the Right Person > for me to send a small suggestion for the Handbook to? If you wish to open up a problem report, please use Bugzilla, e.g., https://bugs.freebsd.org/bugzilla/enter_bug.cgi?product=Documentation . Otherwise, a post to freebsd-doc@ might be helpful. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: Where is 10.2-STABLE?
On Thu, Mar 31, 2016 at 10:32:45AM +1100, Jason Tubnor wrote: > 10.3-RELEASE has been available for a few days now No, it hasn't. The bits for what _may be_ 10.3-RELEASE, barring the finding of any last-minute problems, are what is there. In at least one previous release cycle, last-minute problems *were* found, and the bits had to be re-spun. The release is not official until a signed email from the release engineering team says it's done. (I'm afraid someone has to reiterate this right at the end of every release cycle.) mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: sshpass
Please submit this via bugzilla so that it will not get lost in all the mailing list traffic. Thank you. mcl ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: 10.2-Beta i386..what's wrong..?
On Fri, Jul 24, 2015 at 12:43:43AM +, Glen Barber wrote: Even on amd64, you need to tune the system with less than 4GB RAM. The only correct answer to how much RAM do you need to run ZFS is always more AFAICT. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 10.2-Beta i386..what's wrong..?
On Fri, Jul 24, 2015 at 02:19:20AM +0200, Michelle Sullivan wrote: Why is zfs on i386 so hard? zfs is a resource hog. i386 is not able to handle the demand as well as amd64. I have never, ever, heard of anyone who has a deep understanding of zfs on FreeBSD recommend anything other than amd64. (Note: I am not such a person, so I am simply reporting my understanding.) FWIW, I tried it once. Once. After spending a few days inspecting all the bullet holes in my feet, I moved it off that i386 machine and all the bullet holes healed up. tl;dr: zfs/i386 Not Recommended. But YMMV. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: New FreeBSD snapshots available: stable/10 (20150625 r284813)
On Wed, Jul 01, 2015 at 11:34:17AM -0400, Kurt Lidl wrote: Of course, with no network connection, it's not a very useful machine, There are PCI slots on mine :-) ok, joking aside, this is indeed not useful. But it's useful to note that a couple of months ago, I was running my v245 hard, and it was working fine. I won't have time until this weekend to start firing things up and testing here, but I will try. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: CLANG and -fstack-protector
On Thu, Feb 07, 2013 at 11:52:42PM +0100, Jeremie Le Hen wrote: You can do this, it will work for most of the ports but some ports do not honor CFLAGS. Ports that don't honor CFLAGS are broken ports. Having said that, the last time I ran a script that looked for them (and other things like CXXFLAGS), the results were really disappointing. This would be a good project for someone to take on. OTOH this reply is probably more appropriate for ports@. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9
On Fri, Feb 01, 2013 at 11:53:03AM -0600, Brooks Davis wrote: I'm not sure why I'm being jumped on in this weeks old report of a now-fixed problem. I'm sorry, I'm that far behind in email. I did not realize the problem had already been solved. More often than not the problem is simply thrown over the fence for the ports team to deal with. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9
On Thu, Jan 17, 2013 at 09:15:02AM -0600, Brooks Davis wrote: Not unless you consider adding new functions in a reserved namespace (str*) to be ABI breakage. Well, what often happens is that when we add new functions, ports break. I think deciding whether this is or is not ABI breakage is semantics. The fact is that regressions get introduced with these types of changes. The port should have continued to work unless it was recompiled so it should have preferred it's own version of the strnvis symbol. If its makefiles were properly constructed it would have failed to compile due to the signature mismatch. The mantra should be every possible combination of ways that a port's internal build glue can be wrong, is already included in the Ports Collection. In case after case we see fragile code that is written by people who are clearly not professionally trained. They get it to work on their system and then shove it out the door. Claiming that they shouldn't do that is correct but self-defeating. It's just the reality of open-source software. IMHO, the burden should be on whoever makes the change to find out whether or not regressions will be introduced. (And yes, I am very aware that we don't have -exp run capability right now, but this is one of the cases where I would like to suggest it would have helped.) mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 9.1 minimal ram requirements
On Wed, Dec 26, 2012 at 06:02:33PM +0100, Zoran Kolic wrote: Seeing 9.1-RELEASE instead 9.1-PRERELASE or 9.1-RC4 is also a bad suprise for me... I assume it does not look like release is the lack of packages. What you are seeing is behind-the-scenes preparation. The release is official when, and only when, a security-signed email is sent to freebsd-annou...@freebsd.org from the Release Engineering team. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 9.1-RELEASE crashes almost daily; backtraces always list zfs routines
On Mon, Dec 24, 2012 at 10:17:19AM -0800, Derek Kulinski wrote: Yes, but they are 3.5GB each. I attached text dump to GNATS but I can resend it to you We have a limit of 500K on GNATS PRs. For something that huge, a PR database is really not the right place for it -- please post the dumps somewhere and include a URL to them in a followup to the PR. Thanks. Mark Linimon, on behalf of bugmeister ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Will we get a RELEASE-9.1 for Christmas?
On Tue, Dec 11, 2012 at 11:18:44AM -0500, Mark Saad wrote: the ISO are on the master server The release is official when, and only when, a signed email from the release engineering team says that it is. In a past release cycle there was indeed a last-minute fix that had to be made after the ISO had already started propogating. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 10-CURRENT and 9-STABLE snapshots
On Wed, Oct 10, 2012 at 07:04:22PM +0200, Claude Buisson wrote: As an addon, according to lists.freebsd.org, svn-ports have not been updated since more than a day... This is an unrelated problem, caused by machine upgrades/moves at our main data center. - the recently created snapshots.glenbarber.us is much more limited The intention is to get these snapshots officially blessed. This is one step in the direction. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Clang as default compiler
On Tue, Sep 11, 2012 at 11:49:24PM +0200, Andreas Nilsson wrote: Is there a specif PR to use for ports that fails with clang and does not specify to use gcc ( devel/cdecl and deskutils/calibre so were the culprits so far) There is no specific PR. We have not yet placed the requirement on our ports maintainers to deal with clang. For most of the failures, we are already aware of them, as a result of our periodic runs. So, just filing a PR to say broken on clang doesn't really help us all that much. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Clang as default compiler
On Wed, Sep 12, 2012 at 08:00:46AM +0100, Chris Rees wrote: We don't want thousands of PRs duplicating the information from a simple list of failures. Thanks, that was the point I was trying to make. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Clang as default compiler
On Wed, Sep 12, 2012 at 11:54:51AM +0300, Alexander Yerenkow wrote: How about run automated test on two poudriere setups, one with CLANG set up, other with USE_GCC=4.2 applied to all ports which marked as broken, We have been running various tests for quite some time. Is there somewhere list of these clang-failing ports? http://wiki.freebsd.org/PortsAndClang . I have been maintaing and updating this for over a year now. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Who is responsible for Heimdal/Kerberos in FreeBSD
On Fri, Aug 03, 2012 at 12:51:17PM +0100, Attila Bogár wrote: On 02/08/12 16:04, Chris Nehren wrote: Rather than sending repeated mails to the list (which you've already seen get dropped on the floor), consider using the proper channels for reporting bugs. Send a PR. See http://www.freebsd.org/send-pr.html for more information. Unfortunately I have to disagree with you. You should have initially been directed to the following file, where various committers can claim various parts of the src code: http://svnweb.freebsd.org/base/head/MAINTAINERS?view=log That's the good news. The bad news is that no one has claimed those two areas. Certainly I can report another PR with the problems I spotted and wait 2 years before I get an answer, but I don't call that problem solving. I understand your frustration. Right now we have far more Problem Reports than we have committers to handle them. However I think, it's more sad, that the freebsd developer community is just ignoring the patches they are sent and doesn't considers quality assurance. It's not that they are ignored. It's that we lack sufficient manpower to process them all. For instance, we have no paid staff to look after Problem Reports, even the ones with patches. I am hoping that when we replace GNATS that it will finally be possible for people to vote on problems that they would like to see fixed. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
On Tue, Jun 05, 2012 at 12:18:33PM +0700, Erich wrote: I did not know this. Do you have a link for this? I never read about it. The EOL announcements have them. I don't think the release announcements do, however. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
On Tue, Jun 05, 2012 at 01:00:45PM +0700, Erich wrote: All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched. If you create a branch, you must create a tag for that branch. However, you can create a tag without creating a branch. That is what is done for the ports tree. It's not particularly easy to see this on cvsweb. But let's take a look at a random Mk/bsd.*.mk file via 'cvs log': RCS file: /home/FreeBSD/pcvs/ports/Mk/bsd.apache.mk,v Working file: bsd.apache.mk head: 1.36 branch: locks: strict access list: symbolic names: RELEASE_8_3_0: 1.35 RELEASE_9_0_0: 1.33 RELEASE_7_4_0: 1.26 RELEASE_8_2_0: 1.26 RELEASE_6_EOL: 1.26 [...] RELEASE_6_1_0: 1.9 RELEASE_5_5_0: 1.9 keyword substitution: kv total revisions: 36;selected revisions: 36 description: revision 1.36 date: 2012/05/23 08:17:48; author: miwi; state: Exp; lines: +2 -2 - Remove emacs mode, -*- mode: ...; -*- [1] - Comments for BUILD_ and RUN_DEPENDS fail to mention alternate means to specify dependencie [2] - Fix make reinstall [3] - Trivial comment change for PORTDATA [4] [...] and so forth. The line RELEASE_8_3_0: 1.35 tells you the version of this file as of tag RELEASE_8_3_0 was r1.35. So that's what's on the 8.3R distribution media. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
On Tue, Jun 05, 2012 at 03:23:01PM +0700, Erich wrote: But is this true for apache only or for the whole ports tree? Entire tree. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
One doesn't have to live at the bleeding edge with ports if one doesn't want to even when compiling. One can live a day, a week, a month behind the bleeding edge and allow other to hit problems and report them. To be pedantic, there's a lot of difference between reporting problems, and supplying fixes. Sometimes figuring out the fixes is beyond the capabilities of our maintainers, of course. People should feel free to ask for help on the mailing lists or forums in those cases. But our general problem won't be solved merely by tagging. There have to be people willing to test based only on whatever tree, or branch, or whatever, has been tagged. This is on reason why the tree at release time is _somewhat_ more stable: we are asking people to test, test, test. (The fact that we slow down the rate of major changes to the tree accounts for the rest.) mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Implications of pkgng, was Re: Why Are You NOT Using FreeBSD ?
On Sun, Jun 03, 2012 at 09:31:19PM +0200, Mel Flynn wrote: Once the base system supports binary upgrades of packages through pkgng it should solve a lot of issues that people have with production systems now IMHO, s/solve/expose/ :-) It will then be up to use to solve them. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD ?
On Sun, Jun 03, 2012 at 07:24:11PM -0700, Dave Hayes wrote: I see features and pkgng and things being offered up as solutions... these are all well and good, but in my opinion more comprehensive documentation and support in these areas would do more good than pkgng. IMHO pkgng and optionsng are necessary, but not sufficient, to solve our current problems. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD?
On Mon, Jun 04, 2012 at 07:49:02AM +0700, Erich wrote: can you still install the ports tree and its applications on a FreeBSD 4.4? No. When 4.11 finally went EOL on 01/31/2007 we removed all the compatiblity code, because by that time supporting both was increasing the maintenance burden on our port maintainers (probably in the range of 25%-50%). This was due to how much that the src and ports infrastructure had changed between 4.X and 5.X: different patches had to be kept for each branch, for instance. (This has been much less the case since then; 5.X had some very disruptive changes.) FWIW, according to my research, 4.4 was released 09/19/2001 and probably went EOL sometime in 2003: http://people.freebsd.org/~linimon/schedule/milestones.html The current status is that we support 8.x and 9.x well. Ports support for 7.x is starting to fade over time as new upstream releases rely on newer APIs. 6.x went EOL 11/30/2010 and we no longer claim to support it in ports. I only see many XP machines at the client side running the latest Office applications. Not to disagree that this is possible, but my own experience (with Quicken) is that I was finally forced to move off 2K/XP to be able to continue running their software the way I expect to run it. Without doing any research to back up my claims, I think 2K is from the same timeframe as 4.4. Please don't take any of the above as criticism. It's clear that our model of everyone must run the current ports tree failed long ago. We have some things in progress (pkgng; conversion to SVN, which allows much cheaper tagging/branching) that are key pieces of being able to fix this; others are coming. In the meantime, your criticisms about this facet are absolutely on-target. However, for anyone who expects to be able to run current applications on a 10-year-old OS release, there is no realistic choice other than an OS from a commercial company where there is a revenue stream to support a paid support staff dedicated to that task and that task only. FreeBSD does not have that now and is extremely unlikely to have that in the future. For anyone who has that criterion, we're the wrong choice. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD ?
On Sun, Jun 03, 2012 at 01:43:43AM +0200, Fritz Wuehler wrote: So there could be lots of overlap and just looking at the two numbers you posted doesn't really tell the whole story. No, I agree that it doesn't. I was just trying to add an aside, and point out that the task would not be trivial. Since I'm heavily invested in FreeBSD ports I think I need to step back and let other folks comment in this thread. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Why Are You NOT Using FreeBSD ?
On Fri, Jun 01, 2012 at 05:20:39PM +0200, Nomen Nescio wrote: Maybe FreeBSD should consider migrating to pkgsrc? I'm not arguing that your other points are invalid (in particular, I agree that the xorg change was really painful, and for a long time amd64 lagged i386 badly), but there is one very major blocker for this particular idea. If you browse the following URL: http://wiki.freebsd.org/PackageSystemsComparison You'll see that pkgsrc is around 12k packages. Although our graph is stale, per the portsmon/FreshPorts URLs, we're approaching 24k ports. So: while it's been suggested before, it's not really workable. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: 9.0-RELEASE amd64: No Boot on VMWare Workstation
On Tue, May 15, 2012 at 08:12:05PM -0500, Larry Rosenman wrote: Would it be possible for the next 9.x release to set hw.memtest.tests=0 when we discover we're under a hypervisor to avoid doing the tests? (or default it to 0 in the installer kernel?)? Actually, that's already been fixed, and will first appear in 9.1. I've written up what you can do to patch out the offending test in the meantime: http://wiki.freebsd.org/VMWareBootupSpeed mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Request for flowtable testers and actionable feedback RE: flowtable usable or not
On Mon, Mar 05, 2012 at 02:28:37AM -0300, H wrote: because you don't care about what really matters, people, users, you do not even know how to talk to them I've been criticized for saying this to a user before, but I'm going to repeat it here regardless of consequences. I'm sorry, you (as a user) do not have the right to flame someone in this manner and then expect them to listen to further input from you, no matter how reasonable your further contributions are. We are not paid employees, who might have to simply continue to work with you because their business requires it. I am not speaking for Kip here but I will state that I myself am happy to work with users up until I feel I am getting treated like this, at which point I feel no further obligation whatsoever to try to help them. Executive summary: you are being very rude here. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: flowtable usable or not
On Sat, Mar 03, 2012 at 03:44:42AM -0300, H wrote: nobody want to read, they want a desktop nothing else, something silly and easy to read email and write docs and surf on the net, listen to a CD, they need to put a cd into the drive, running install process, reboot, using, nothing else and such a thing ... we do not have I really recommend this class of users investigate PC-BSD. It works right out of the box (all the type of work you are frustrated with has already been done, and is part of their release process). To my view, comparing FreeBSD to Ubuntu is apples-to-oranges. A much better point of comparison is PC-BSD to Ubuntu. I can't speak to whether or not PC-BSD will meet all your needs, but it is much more oriented to users than stock FreeBSD. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ports usable or not [was: flowtable usable or not]
On Sat, Mar 03, 2012 at 09:08:28PM +0100, Nomen Nescio wrote: Thanks mcl. I am off on other things for now but I will file PRs next time I come across something. In the past I have emailed the port maintainer and the answer is usually yeah I know. After a few of those I thought filing PRs is a waste of time considering the maintainer doesn't seem to care. Once PRs are filed, we are able to track them and if the maintainer does not work on them after a period of time, it's fair game for other people to work on them as well. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ports usable or not [was: flowtable usable or not]
On Fri, Mar 02, 2012 at 03:35:24PM +0100, Nomen Nescio wrote:
If you use [!i386] you are likely to find problems with ports and
this gets amplified if you use nonstandard (read stuff not everybody uses)
ports.
Fair enough.
I have found several ports broken for many releases in a row.
These are bugs. Please report them via PRs.
Other ports aren't supported on certain target architectures but the build
doesn't tell you that until after it has run for a couple of hours
Those are also bugs. Please send PRs for those, as well. I am particularly
concerned about amd64 in this regard (although I am actually only myself
doing the package runs for sparc64 and powerpc). We continually try to
adjust the metadata for ports to indicate where they will and will not
run, based on the output of pointyhat runs. (OTOH pointyhat runs the
src tree from the oldest supported minor release on each branch, so
this may be a clue .)
For those interested in investigating the metadata as seen by these
package build runs, they are available. For instance:
http://pointyhat.freebsd.org/errorlogs/amd64-9-latest/duds.verbose
Substitute {i386|sparc64|powerpc} for amd64 and {7|8} for 9 to
look at the others.
Note that I haven't done any ia64 builds in quite a long time. Also
note that for sparc64 and powerpc, I no longer try to do 7. Finally,
we haven't done many runs on 10 yet.
You can see the overall state of the various package builds at:
http://pointyhat.freebsd.org/errorlogs/packagestats.html
whose skipped links will take you to the duds.verbose files.
mcl
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ports usable or not [was: flowtable usable or not]
Yeah, I've been trying to prioritize some -exps that are blocking other people right now. I know there's many more :-) mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD9 and the sheer number of problem reports
On Sun, Feb 26, 2012 at 06:32:17PM +0700, Erich Dollansky wrote: There's no such odd/even number policy with FreeBSD-- I think you're thinking of another OS ;) maybe something got stuck in my head with the move from 4 to 5. Yes, 5 was the Great Leap where true SMP was introduced. In the many-year-long development cycle, so many other things (IIRC geom and suspend/resume, among others) that the change from 4 to 5 was completely disruptive. We resolved to release more often so as to never be in that situation again. (Granted, probably no architectural change will ever be that sweeping again.) There is no meaning to odd/even release numbering in FreeBSD. How easy was the move to 6 then? An order of magnitude easier than the move to 5. Although as needs to happen with each major release, some code that had been deprecated was dropped, and some subsystems which no one stepped up to do the maintenance necessary for other re-architecting were dropped as well. Each of the subsequent moves has been much the same -- a few gotchas, but nothing like the move to 5. This has been purely intentional. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD9 and the sheer number of problem reports
On Sun, Feb 26, 2012 at 09:27:58AM -0300, H wrote: it is release engineering who could establish a little bit more time between code-freeze and RELEASE As you will see from the (very) long discussion that you are about to read, there has to be a compromise. As it was, the release process was too long, not too short. Yes, we would like to get more testers pre-release, but that seems to be more easily said than done. Ideas appreciated. You will also see in the thread that: - it is not possible to release bug-free code, and in fact - it is not possible to release code with no regressions whatsoever if you are to ever release anything at all. To summarize: yes, we do care: and yes, these are classical software engineering problems that can only be dealt with, not solved completely. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Odd reboot problems with 9.0-RELEASE i386
On Fri, Jan 20, 2012 at 07:23:35PM +0200, Andriy Gapon wrote: I think that it probably could be easier for you and for those reviewing your kernel config if you 'include'-d GENERIC into your kernel config and then used device/nodevice, options/nooptions, etc to make your customizations. I strongly recommend this path. It took a long period of time to factor out the crazy kernel configs that were used all over the package building nodes. The stuff that changed wound up only being ~15 lines, 10 of which were common to all nodes and archs. The rest were minor tweaks. But there was no way to tell that without a lot of detective work. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
status of ports and clang
I have recently been able to get the new build cluster on pointyhat-west set up to run full builds of ports with clang on amd64-9. I have documented the latest results on the wiki: http://wiki.freebsd.org/PortsAndClang If you are interested in working on ports being built via clang, this is your place to start. Please also note that now that we have up-to-date builds going, it is not as useful to us to report individual clang build failures. Patches to fix problems are, of course, highly welcome. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: SCHED_ULE should not be the default
I'm not on the Release Engineering Team, and in fact don't have a src commit bit ... but this close to a major release, no, it's too late to change the default. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: bin/139146 still not right in FreeBSD 8.2 (-m32 on amd64)?
On Wed, Mar 09, 2011 at 03:15:39PM -0500, Thomas David Rivers wrote: But, when I try to build 32-bit programs I get problems linking, and I stumbled onto PR bin/139146. That one was closed as a duplicate of gnu/112215. I've forwarded your email to GNATS with the followup redirected there. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Support for Areca ARC-1300-4X on 8-STABLE?
On Wed, Nov 24, 2010 at 10:01:31AM -0500, Paul Mather wrote: I'd also hope that such a vendor would be contributing its drivers directly into the source tree rather than having a separate set of patches or downloads for end-users to fiddle about with. In a perfect world, yes, but not all vendors currently do this. The have their own release cycles and source repositories, as we have ours: in some cases, it takes a non-trivial amount of effort to coordinate the two. I'm always happy to see closer cooperation, of course. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Can't build boot blocks after new GPT attributes added
On Wed, Oct 27, 2010 at 09:27:03AM -0400, John Baldwin wrote: Maybe you could add text to the handbook to say this, but it is already implicitly assumed in the handbook section you are referring to since it assumes you can safely compile a new kernel, etc. [...] If we were to document those every time it would clutter documentation making it harder for someone who is new to FreeBSD to simply setup a serial console on a box that they just installed. It sounds like what we need is a tutorial, and (somewhere else?) the extended version. People seem to trip over things like this fairly often; at least this way we could refer them to a standard text. No, I don't have the backgroud, or cycles, to write it :-) mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: HEADS UP: FreeBSD 6.4 and 8.0 EoLs coming soon
The reason is performance for overall network stack, not ideology. For a practical reasons, it works but slow is better than doesn't work at all (due to absence of code in the src tree). Make it work. Make it right. Make it fast. In that order, know this? Sacrificing work for fast?.. Hmm, if it is not ideology, then what is it?.. It wasn't it works but slow. It was it works, but networking throughput is limited on the modern hardware that the majority of our users employ. In particular, IIUC, 10GB network drivers were suffering under the old strategy. We simply were not competitive with other OSes, and we have many multiples more users interested in 10GBE than in ISDN. You do not understand the problem. It is not in notices volunteers, but rather in the Project's policy - delete something which could still work. You do not understand how this was handled. The situation was: an announcement was made that in X months, all network drivers need to be made to run Giant-free so that FreeBSD can drop Giant from the neworking stack to move forward. Within that period, most of the drivers were updated. Repeated postings were made to the mailing list that the following drivers still have not been converted, and need to be updated or they will be dropped. They weren't; they were droppped. So while it could still work, it was slowing down progress. The fact of the matter is, FreeBSD is a big project with a finite number of developers. We try to keep as much coverage of systems as we can, but a reality of any large software engineering project is that older features sometimes have to be dropped to make progress. The code still exists in the repository for any interested party to pick up and modernize. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ports
On Fri, May 28, 2010 at 02:16:31PM +0300, Gregory Edigarov wrote: Which is the minimal current version of system supported by ports? We are currently supporting the same systems that secteam does, so, for each branch, 6.4, 7.1, and 8.0, respectively. The secteam matrix can be found at http://www.freebsd.org/security/index.html#supported-branches . However, note that as individual ports are updated, they are becoming less and less compatible with the base system in 6.4, and are thus being marked 'broken'. Since the 6.x branch is only a few months from EOL, IMHO people should start moving away from it as soon as feasible. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD Release 8.0 floppy images
You can still build them. They just won't be built by default. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Can't boot after make installworld
On Mon, Mar 22, 2010 at 08:41:35PM +, Krzysztof Dajka wrote: But still I am confused with FreeBSD naming and it's relation with tags which are used in standard-supfile. Please see the following for an overview: http://www.freebsd.org/doc/en_US.ISO8859-1/books/faq/introduction.html#CURRENT The definition of the -STABLE branches is that we try to keep the interfaces to the kernel stable. While this helps also keep the src tree itself stable, from time to time regressions will be introduced as changes are merged back from the -CURRENT branch. So, for the src tree, there are: - releases, which are not updated; - releases plus security fixes; - -STABLE branches; - the -CURRENT branch. The ports tree is not branched, so you can consider that everything is current. If you need to stay with a ports tree that is more tested, you'll need to stay with the ports tree that came with a -release. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Complete ports thaw
It probably bears repeating that the tree will be unstable for the next few days while a number of large commits hit the tree. These were held off during the release process to make life easier in case portmgr had to do tag-slips. Image processing libraries, xorg, kde, and gnome are scheduled to be updated, among others. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: posting coding bounties, appropriate money amounts?
On Fri, Jan 22, 2010 at 07:20:18PM -0600, Adam Vande More wrote: I'd be willing to put up a thousand USD or possibly more depending on what sort of work was being considered. I suppose a better choice would be for someone here to make a list of issues which the community feels need attention, and put the pooled donations to whatever things had highest priority -- or, if that isn't plausible, then to what interested developers wanted to work on. To the best of my understanding, that is basically what donating to the FreeBSD Foundation accomplishes, although it would be nice so see some more transparency in their decision making process. As stated earlier in this thread, for tax reasons the Foundation can't be in a position to pass through specific funds targeted to specific projects. IMHO there's plenty of room for experimenting with different ways to get projects funded, especially for small specific task xyz needed. I can't really one of the people to try to set up such things, since I want to be one of the people taking advantage of it. A good first task would be for someone (TM) to put up a web page for tasks that the community would be willing to fund, with a sign-up sheet for volunteer donors, to gauge general interest in # of people who would be willing to contribute to particular tasks. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Are there schedules for 7.3-RELEASE?
On Thu, Jan 07, 2010 at 12:11:30AM +0100, Miroslav Lachman wrote: Are there (when will be) plans for 7.3-RELEASE as was for 7.2 on this page: http://www.freebsd.org/releases/7.2R/schedule.html ? Dates are currently under discussion. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Using RELENG_8 to compile for older RELENG_x
On Wed, Dec 16, 2009 at 11:28:51AM +0100, Roland Smith wrote: the current ports tree isn't guaranteed to work on [4.x] either. s/isn't guaranteed to/is guaranteed not to/ (sorry) You might want to experiment with checking out a ports tree as of tag RELEASE_4_EOL and trying to pull in newer pieces from there. But basically, you're trying to piece together modern ports with something that was released 01/25/2005 and went EOL on 01/31/2007 (coming up on 3 years ago). mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Using RELENG_8 to compile for older RELENG_x
On Wed, Dec 16, 2009 at 12:54:52PM +0100, Roland Smith wrote: In the days before 5.3 or even 6.0 I could understand why people clung to 4.x. But now it seems like inviting trouble. 5.3 still had a lot of sharp edges (a lot of things were merged into it just prior to release). But at this point, we're even phasing out 6.x. Really, I would hope that everyone except people embedding FreeBSD into their products (and thus have long development cycles) would be on 7.x by now. It has a much better chance of running on modern hardware. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ACPI Error: A valid RSDP was not found 20090521 tbxfroot-309
On Thu, Dec 10, 2009 at 08:48:31AM -0500, John Baldwin wrote: Hmmm, there isn't anything CPU-specific in ULE vs 4BSD, and I would expect ULE to work fine on a PIII. I would generally expect device timeouts to be more of a driver issue than a scheduler issue. We've run nodes in the package build cluster on ULE for years. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: NSIS compile failed on FreeBSD 7.2
On Fri, Nov 20, 2009 at 11:46:13AM -0800, Jeremy Chadwick wrote:
If that's indeed the case, then the port Makefile needs to be modified
to reject building on any architectures other than i386. This should
suffice:
ONLY_FOR_ARCHS= i386
There's a (fine?) distinction between the usage of IGNORE (which
*_FOR_ARCHS drives) and BROKEN. The former is more of a statement
of it will never work; the latter is more of a statement of it
doesn't work right now.
So, in my own patches for e.g. sparc64, I use
.if ${ARCH} == sparc64
BROKEN= Does not compile on sparc64
.endif
unless the port bails out of config with arch not supported, or it's
clearly i386-hardware-related, or something like that.
I recognize that this may be a matter of personal taste.
mcl
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD 7.2 Release process starting...
On Sun, Mar 22, 2009 at 09:18:03AM +1100, Aristedes Maniatis wrote: Is there any way to automatically create such a page from the bug tracker? Not that fills in the dates, no. We are working on a prototype to track particular PRs. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
reminder: bugathon upcoming this weekend
Starting this Friday, we are going to hold a bugathon to work through some of the network-related PRs. More details, and a list of resources, are available at http://wiki.freebsd.org/Bugathons/January2009. I have come up with a page that details a subset of those PRs as a set of suggested PRs: http://people.freebsd.org/~linimon/annotated_prs_bugathon.html Please join us to work through some PRs. Thanks! mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Big problems with 7.1 locking up :-(
On Mon, Jan 19, 2009 at 04:59:59PM -0500, Pete Carah wrote: I shouldn't *have* to kernel debug for a normal usage of an official release. Agreed, but the problems that people are having do not seem to have arisen on any of the systems that ran prelease tests for 7.1. Although I'm sure it does not seem that way to you, 7.1R had a very long QA cycle, and as far as I knew all the showstopper issues had already been addressed (although I don't officially speak for re@, I'm just an observer.) With my bugmeister hat on, I'll happily accept suggestions about how we can get more people involved in testing the prelease images. Clearly the situtation we're in right now is not where anyone wants us to be. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: visibility of release process
On Mon, Dec 08, 2008 at 08:57:37PM +1100, Aristedes Maniatis wrote: 3. Improvements to the bug tracker. Personally I'd love to see something like Jira used [4] with all the sophistication of workflow, release notes, voting for bugs, etc, etc. I have some notes for some prototyping ideas, but I've been involved in package building issues more than bugbusting issues lately. I think it's time to task-switch ... mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
(no subject)
On Wed, Sep 24, 2008 at 09:32:52AM +1000, jonathan michaels wrote: thank you gentle peoples for working out this solution. Unfortunately it has not been 'worked out' with the decision-makers. It has been suggested. Doing s/suggested/agreed to/ is not an automatic process. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Upcoming Releases Schedule...
On Tue, Sep 16, 2008 at 04:30:26PM +1000, Andrew Snow wrote: I think FreeBSD is getting in a difficult position now because there's so much cool new stuff being shoe-horned in, but without the necessary volume of contributors to back it up with testing and bug fixes. We're interested in suggestions about how to get more people involved with testing and bug fixes. There's certainly no lack of demand for the features -- all the way from running on inexpensive wireless routers all the way up to 'enterprise- grade' distributed storage solutions. (These are real examples from various mailing lists.) So, in your opinion, what's the way to reconcile all these demands (features + stability + long-term support of release branches) with a group that is 95%-plus volunteer effort? mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: FreeBSD 7.1 Content
On Sun, Sep 07, 2008 at 08:06:24AM -0400, Randy Pratt wrote: Additionally, I've never seen a clear way of synchronizing a local ports tree to that used to create the LATEST packages. There's really not a way to easily track this, especially with the fact that we tend to run incremental updates. The best approximation we can give you is e.g.: http://pointyhat.freebsd.org/errorlogs/amd64-6-latest/cvsdone but if there were manual updates to the tree, then the cvsdone files may be out-of-date. In addition, if there were checkins in progress as of that time, the tree may be inconsistent in the first place :-/ I used to have a page that indexed those and a lot of other statistics but it is currently broken. I need to put fixing that on the TODO list. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Fwd: FreeBSD 7.1 Content
On Mon, Sep 08, 2008 at 10:27:31PM -0400, Randy Pratt wrote: Personally, I quit using packages in the 2.x-3.x days since there were far less problems building everything from sources and not trying to mix pre-built packages and locally built ports. We are doing much better these days in terms of building packages quickly, especially on amd64 and to some extent i386. More hardware has helped. However, with over 19,000 makefile and makefile parts involved, there's really only so much that can be done outside of the QA/freeze timeframes. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sun4v arch
On Sat, Aug 23, 2008 at 06:52:07PM -0700, Maxim Sobolev wrote: There is a better interpretation, which is that the only critical issue is lack of real users for this port, not lack of serial port support :). My understanding is the the port is in a pre-alpha state due to unfinished work in the kernel, so expecting there to be any userbase is premature. All of our 'new' architectures which are in this state have so few non- developer users that there is hardly any reason to submit PRs. AFAICT the active developers already know what's missing :-) Our implementation of GNATS barely serves us as a problem report system; it fails almost completely as a system for listing missing features. We would need to have something like that to track the status of the non- Tier-1 ports. (I used to maintain a table of how feature-complete the various ports are, but it is now way out of date.) mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
new wiki page to collect information about the ATA subsystem
Jeremy Chadwick (koitsu@) has been gathering together information on the wiki about commonly seen problems with FreeBSD: http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues http://wiki.freebsd.org/JeremyChadwick/ATA_issues_and_troubleshooting Based on a discussion on #freebsd-bugbusters, I've gone ahead and added a signup page for people that are interested in volunteering to do ATA regression testing (either for patches that are included in the various PRs, or for isolating regressions that have already happened): http://wiki.freebsd.org/ATA/ATA_Volunteers Please feel free to sign up if you're interested in helping on this. Perhaps it will lead to something. There is also a new meta-page to cross-reference the above: http://wiki.freebsd.org/ATA mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: challenge: end of life for 6.2 is premature with buggy 6.3
kris points out that I botched my reply by confusing contributions from 2 different posters. My apologies (I have not closely tracked the entire thread). Nevertheless, the URLs and the summary information should still be of interest. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: challenge: end of life for 6.2 is premature with buggy 6.3
On Thu, Jun 05, 2008 at 05:39:36PM +0200, Kris Kennaway wrote: You seem awful hostile - do you really think that's the best way to represent the project you're involved with? When confronted with what you are doing is wrong, but I am not going to tell you what it is because if you cared you'd already know (my summary of your past postings in this thread)? Possibly not 'best' but 'understandable'. The option provided seems like a fairly good compromise to both interests. Pick 6.3 (or anything the release team wishes) to support for a longer period of time. If you want FreeBSD to be supported the same as a commercial product, and you be able to dictate the terms, then it's not going to happen completely via volunteer effort. At some point some money is going to have to change hands. Either you pay someone at your company to do support, or you hire someone external. Then you get to dictate what is supported and for how long. Otherwise, all you can do is to suggest. A consensus statement signed off on by one person is the former -- not the latter. Now to add my own frustration to the list ... I next note that _after_ you said you had no more time to continue with this thread for now (and thus could not yet give us pointers to specific failures and any corresponding PR numbers), you are still replying to email. Since you still seem to have some time, let me help you do a little research here. Checking the PRs that you have submitted that are still current, none of the src-related ones are from anything newer than 6.0R: http://www.freebsd.org/cgi/query-pr-summary.cgi?originator=Jo+Rhett There are some resources to help you find already-submitted PRs to reference if it will help. (The latter 2 are new, and are attempts by the bugbusting team to flag 'well-known problem' and 'PR indicates regression'): http://wiki.freebsd.org/JeremyChadwick/Commonly_reported_issues http://people.freebsd.org/~linimon/studies/prs/well_known_prs.html http://people.freebsd.org/~linimon/studies/prs/prs_for_tag_regression.html Now I'll admit the following is a less-obvious query of the database, but it's my attempt to show regressions that we have already flagged in 6.3: http://www.freebsd.org/cgi/query-pr-summary.cgi?release=%5EFreeBSD+6.3category=kerntext=regression So these 4 links should give you some quick ways to generate some PR numbers for us. Finally, here are some statistics about PR count: rel all kern --- --- 6.0 210 91 6.1 217 81 6.2 396 102 6.3 167 56 7.0 563 140 To me, this doesn't look like an overwhelming case for 6.3 being worse off than 6.2. Yes, I'm sure there are regressions: there are in any release. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: ad0 READ_DMA TIMEOUT errors on install of 7.0-RELEASE
On Thu, Feb 28, 2008 at 02:47:28PM +, Chris wrote: Did they push ahead with release because waiting for the mia dev? There's a lot of things that go into deciding when to release. The release cycle this time was not supposed to be as long as it was. We kept finding showstoppers and needing to go back and fix them (especially for things like TCP performance and stability). However, sooner or later you do have to release something. There are bugs in every software program ever released. It seems that in certain cases (we're not sure exactly which) the ata subsystem has regressed. There's debate on the lists about exactly how common this is: with bugmeister hat on, I don't think it's as common as some folks seem to think it is (otherwise we would be overwhelmed with bug reports). There's a lot of badly-written firmware out there, and a lot of workarounds for it in the current ata stack. I'm not familiar with the code, but fixing all this is a totally non-trivial task. Of course it would be nice to have several committers with sufficient variety of boards, and time, and experience to do a lot more QA, but we're a volunteer project and have to go with what we have in some cases. I'm open to suggestions about how we can get more people involved in QAing ata. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: make KNOBS
On Mon, Feb 25, 2008 at 09:55:22PM -0800, Chris H. wrote: Is there, or does anyone maintain a KNOBS list possibly categorized by application/port/version, etc...? ports/KNOBS? mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 7.0-RC2 package glitch
On Sat, Feb 16, 2008 at 03:13:35PM -0800, Wayne Chapeskie wrote: The RC2 sysinstall misses six packages, which are included on disc 1, which RC1 did install: imake-1.0.2_4,1 makedepend-1.0.1,1 gccmakedep-1.0.2 xorg-cf-files-1.0.2_2 xorg-nestserver-1.4,1 xorg-vfbserver-1.4,1 Between RC1 and RC2, sysinstall was cleaned up to install X by using the single top level xorg meta-package rather than the old method of specifying a number of different meta-packages. Unfortunately, the xorg-7.3_1 package in 7.0-release does not pull in the above six packages. There are two differences. imake (which brings in makedepend, gccmakedep, and xorg-cf-files) is only a BUILD_DEPENDS of the xorg metaport. If you're simply installing from packages, you won't need them. If you want to rebuild them at any future time, you will. vfbserver and nestserver are depended on by 4 and zero ports respectively, none of which are in the xorg metaport. They'll only be brought in if you need one of them. So, AFAIAC, this is working as designed. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: /usr/bin/objformat is missing
On Mon, Jan 28, 2008 at 04:55:01PM -0800, Jeremy Chadwick wrote: I don't agree with any port creating a file in /usr/bin, and it's safe to say others will not agree with it either. In particular, portmgr will mark such a port as BROKEN :-) mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
fwd: [EMAIL PROTECTED]: results of the 20080125 bugathon]
Here's a repost of the message I just sent to [EMAIL PROTECTED] Followups there, please. Thanks. mcl - Forwarded message from Mark Linimon [EMAIL PROTECTED] - Over 30 people participated in this bugathon. Thanks to all who participated! During the 3 days, we closed around 120 PRs, and probably 50 more were set to feedback. Of course, during this time about 80 PRs came in (including some ports PRs). While the net reduction doesn't look that large, it does constitute positive progress -- a large number of stale PRs were indeed closed, and a few were committed. For our next bugathon we'll try to be more focussed on committing some of the PRs that we've already identified, and also to keep a count of PRs busted by category (which we had done before, but forgotten to get a volunteer for this time.) As part of the run-up to the bugathon, several new wiki pages were created: http://wiki.freebsd.org/Bugathons/January2008 http://wiki.freebsd.org/Bugathons/January2008/InterestingBugs http://wiki.freebsd.org/BugBusting/Resources http://wiki.freebsd.org/Bugbusting/TipsAndTricks http://wiki.freebsd.org/BugBusting/Volunteers http://wiki.freebsd.org/KernelBugTriage Please take a look at these if you're interested in coming up to speed with what we're up to. Thanks! mcl - End forwarded message - ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
upcoming bugathon this weekend
If you're interested in helping out on our PR database problems, please see my posting on freebsd-bugbusters@: http://docs.FreeBSD.org/cgi/mid.cgi?20080125182651.GA9914 We're having a bugathon this weekend, with the agenda being mostly to figure out where we are, who would like to help, and coming up with ways that they can do so. Followups to freebsd-bugbusters@, please. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD 6.3-RELEASE Available
On Fri, Jan 18, 2008 at 03:51:43PM -0500, Ken Smith wrote: Due to resource limitations (both human and computer) there won't be an ia64 6.3-RELEASE but there will be an ia64 7.0-RELEASE. Unless something changes rapidly, ia64-7 will not have any packages shipped with it: the last I tried, it was unable to build any. Anyone who is interested in working on this should contact me off-list. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.3-RELEASE
On Thu, Jan 17, 2008 at 01:59:01PM -0800, Josef Grosch wrote: I have a mirror at work (Juniper Networks) and we have had all the bits since Tuesday. You can't have; the final sparc64-6 packages were just finished yesterday, at the last second. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 6.3-RELEASE
On Tue, Jan 15, 2008 at 09:51:13PM +0200, George Kontostanos wrote: So may I guess that we have a release ? This question happens every time we get near a release. There will be a release when, and only when, a signed email is sent from the Release Engineering team to the various mailing lists. In the meantime, final preparations are being made, such as giving the mirrors time to get the bits, so that they will be there when the announcement goes out. Please be patient. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
HEADSUP: new wiki page: State of Packages on Sparc64
I've just posted a message with that title to sparc64@ with crosspost to [EMAIL PROTECTED] If you're interested in deciding on where we're going with sparc64, I invite you to join that thread. (Please don't reply to this message; 2 lists is probably one too many). mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PR backlog [was: Re: usb/umass, devfs: this sucks]
On Sun, Dec 30, 2007 at 01:01:19AM +0100, Alexander Leidinger wrote: Quoting Mark Linimon [EMAIL PROTECTED] (from Wed, 26 Dec 2007 12:04:15 -0600): - The creation of a weekly posting bugs the bugmeister team thinks are ready for commit. This doesn't seem to have attracted the desired attention. Perhaps this is a problem of push not being the right solution here; perhaps it just hasn't been publicized enough. Where is/was this mail send to? To: [EMAIL PROTECTED] Subject: PRs recommended for committer evaluation by the bugbusting team It's sent out weekly. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
PR backlog [was: Re: usb/umass, devfs: this sucks]
On Wed, Dec 26, 2007 at 06:15:16PM +0100, Henrik Gulbrandsen wrote: Fixing and merging are good, but it seems to me (as an occasional patch contributor without commit privileges) that the bottleneck for USB is still in the handling of incoming patches [...] if a one-line fix such as that in usb/78984 has not been applied after more than a year, how long will it take for patches that involve multiple subsystems? I'll put on my bugmeister hat for a moment. First, I share your frustration. Second, unfortunately, it's not just USB. We suffer from this problem in several other areas, notably, patches for the userland utilities (bin). There are two interrelated problems that create a chicken-and-egg situation: - the PR tool is insufficient for our needs; - there's not a culture of going and fixing bugs outside of the code one usually works on. As for 1), once the releases are out, I intend to start working on defining what our needs are. As I've stated before in other places, until we understand those, and get community buy-in to define an actual process rather than just a particular PR system, it's unwise just to change the PR system. (IMHO, there's no reason to further automate a process that doesn't work correctly.) I hope to have something concrete to present at BSDCan in May. As for 2), I've scratched my head for what to do about that for a while, and not been able to make much progress. Here's what we've tried: - The creation of a weekly posting bugs the bugmeister team thinks are ready for commit. This doesn't seem to have attracted the desired attention. Perhaps this is a problem of push not being the right solution here; perhaps it just hasn't been publicized enough. - The creation of a hack for classifying PRs, the [tag] convention. This is simply working around the weakness of the tool. However, it is sufficient to be able to generate weekly email sorting the PRs by tag, and another email showing only PRs with patches, also sorted by tag. If you are a committer, it's also possible to run queries via: ~gnats/tools/showwithtag tagname to get a summary. - Trying to get more traffic on the freebsd-bugbusters@ mailing list. - Trying to create some interest in #freebsd-bugbusters on EFNet on IRC. This has not attracted enough committers to be viable yet. - Holding some bugathons (idea stolen from NetBSD) where we try to get committers to come onto the IRC channel at particular weekends to try to interactively work through PRs. This had some success, but we have not done one in a while. The odd thing is that for ports, the existing PR system -- plus, most importantly, the hacks we've added on top of it -- works reasonably well. - Each port has an explicit maintainer field (even though many of the entries are null). Most of the src codebase does not, therefore no one in particular owns it. - We've taken advantage of that to layer a PR auto-assigner on top, that also sets things to 'feedback'. - portsmon is also able to track PRs by the port they affect, and semi- weekly reminder emails are sent out. But the first of these items is really particular to ports. Also, more ports PRs than src PRs are upgrades/bugfixes, rather than true bug reports that need substantial investigation (in fact, the ratio is probably exactly reversed). This means we can clear a proportionally larger number of ports PRs. All of this has helped get the port PR count down over the last several years, to the point where it no longer seems as overwhelming as the backlog in the other areas. The size of the backlog creates a substantial disincentive to try to fix a handful -- thus perpeturating the cycle. What we all need to understand is that the PR count will never be at zero; if we can instead settle for a steady-state, where the most concrete PRs can be worked on as they arrive, then I'll feel we've have made great progress. Unfortunately I don't have any brilliant insights as to how to make the work more interesting; most of my ideas have the focus of simply making it less frustrating. I'll throw the floor open for brainstorming at this point. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PR backlog
On Wed, Dec 26, 2007 at 12:43:06PM -0800, Richard Neese wrote: Point and Fax I have emaile Sobomax about fixing and updating the asterisk ports. and have sent patches but never got a reply in 9 months. For situations like this you need to email [EMAIL PROTECTED] We already have defined parameters for resetting inactive maintainers. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 2 x quad-core system is slower that 2 x dual core on FreeBSD
On Sunday 02 December 2007, Alexey Vlasov wrote: I used 7.0-BETA3 and it is much worse. Ouch. A lot of systems see improvement. Thanks for trying it out. I hope that one of the people that has been doing the actual work can now comment (I am just an onlooker), and that you can be patient in the meantime. Unfortunately, Kris, who often looks at these kind of issues, is traveling for all of December and thus off the net. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 2 x quad-core system is slower that 2 x dual core on FreeBSD
On Sun, Dec 02, 2007 at 12:37:32AM +0300, Alexey Vlasov wrote: I decided to install FreeBSD 6.2 i386 on one of the servers, and the result was totally non productive. The 6.x series was intended to get us back to the stability that we had had pre-SMP integration. I believe we mostly succeeded. One of the major thrusts for 7.0 development was to fix the performance regressions that had been introduced. From the results that I have seen (I am not one of the participants), there has been major progress over the past 2 years in removing yet one bottleneck after another. Recent tests show us to be on a par with Linux on a number of benchmarks; of course, we need more people testing 7.0 in real-world environments to confirm this. You may want to try the 7.0 release candidate on a testbed to see if your results have improved as much as we think that they will have. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Is it O.K. to use the 7.0 ports tree on 6.3 ?
On Friday 23 November 2007, Pete French wrote: is it safe to simply untar the ports.tgz file from 7.0 on the 6.3 machines, rename INDEX-7 to INDEX-6 and install away, or are there more subtle differences to tran the unwary ? The dependencies can vary depending on OS release, so it's not guaranteed to work. Use 'make fetchindex' after you install to get the latest snapshot for 6-STABLE. mcl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
