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"
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
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.
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
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
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
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.
> > 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
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
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
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
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
> 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"
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
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"
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
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
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
___
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
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
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
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
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
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
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
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.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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,
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
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
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
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
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.
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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,
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
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
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
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
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
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
___
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
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
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
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
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
___
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:
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
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,
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
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
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.
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
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
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
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
___
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
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
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
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
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
___
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
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
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
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
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.
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
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
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
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
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
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.
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
1 - 100 of 170 matches
Mail list logo
