On 10 July CentOS 6 has been, finally, released.
CentOS-6.0 is based on the upstream release of Red Hat EL 6.0 and includes packages from all variants. All upstream repositories have been combined into one, to make it easier for end users to work with.
Written by: Sam Varghese | Published in: Open SourceA senior OpenBSD developer has complained on a mailing list that upstream vendors of free and open source software are adding in changes without any thought of whether downstream users could adapt to the change.
CentOS 6.0, a Linux distribution built from source RPM packages for Red Hat Enterprise Linux 6.0, has been released: "We are pleased to announce the immediate availability of CentOS 6.0 for i386 and x86_64 architectures. CentOS 6.0 is based on the upstream release EL 6.0 and includes packages from all variants.
I'm under the assumption that if I have an upstream connection, if I want a to set it to use keepalive, I need to do so in the upstream block. If I have the keepalive setting set outside of the upstream block (the block being between the brackets where the upstream is defined), is that keepalive used if I haven't set one in my upstream block?
Karanbir Singh has announced the release of CentOS 5.7, a free enterprise Linux distribution built from source code for Red Hat Enterprise Linux of the same version number: "We are pleased to announce the immediate availability of CentOS 5.7 for i386 and x86_64 architectures. CentOS 5.7 is based on the upstream release EL 5.7 and includes packages from all variants including server and client.
As always post any issues you may find with this new kde build, DO NOT post bugs upstream, this is not a final release yet. We want our testers to help us find bugs so the final rls can be as good as possible. We will relay any bugs not related to Chakra errors upstream.Kdepim is not yet included, will be up as soon as build issues are resolved.https://bugs.kde.org/show_bug.cgi?id=3041
We're building a load balanced setup with two load balancers (that also terminate SSL) and several upstream servers. Both the load balancers and the upstream servers run nginx. The network on which requests are forwarded to the upstream servers cannot be trusted, hence we have to re-encrypt it after SSL termination on the load balancer.
Testing is our playground repository, the place we use for testing our builds and detect build problems. Reporting upstream bugs about packages in the testing repository sometimes only gives a lot of job to the developers trying to find a problem maybe caused by a wrong build.So.
I'm just wondering what else you expect to happen here. The issue has been acknowledge and reported upstream, and there's a workaround available in the meantime. This is a very common situation, wouldn't you agree?Other distros might apply patches until upstream provides a fix, but that's not the way Arch works.
Email this page
