Displaying 20 results from an estimated 10000 matches similar to: "CentOS-announce Digest, Vol 125, Issue 10"
2015 Jul 27
0
CentOS Continuous Release Repository updated with CentOS-6.7 RPMs
The packages that will become CentOS-6.7, as well as updates completed
for CentOS-6.7 to date are now released into the CentOS-6.6 Continuous
Release (CR) repository.
All packages except for the centos-release RPM are included.
The purpose of the CR repository is to make the built packages
optionally available to users who opt in while we work on the CentOS-6.7
install tree and all the
2015 Jul 27
3
CentOS Continuous Release Repository updated with CentOS-6.7 RPMs
The packages that will become CentOS-6.7, as well as updates completed
for CentOS-6.7 to date are now released into the CentOS-6.6 Continuous
Release (CR) repository.
All packages except for the centos-release RPM are included.
The purpose of the CR repository is to make the built packages
optionally available to users who opt in while we work on the CentOS-6.7
install tree and all the
2015 Aug 07
0
Release for CentOS Linux 6.7 i386 and x86_64
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
We are pleased to announce the immediate availability of CentOS Linux
6.7 and install media for i386 and x86_64 Architectures. Release Notes
for 6.7 are available at
http://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.7 - we recommend
everyone review these release notes.
CentOS Linux 6.7 is derived from source code released by Red Hat, Inc.
for Red
2015 Aug 07
0
6.7
On 08/07/2015 04:01 AM, ????????? ???????? wrote:
> I don't have CR enabled and a heap of available updates means CentOS 6.7
> has been released or what?
> Did I miss the announcement?
6.7 is there most places ... since we have more than 500 external
mirrors (right now 593) not all of them are updated. (looks like 4%
still are not completely updated)
If we announce too soon, people
2016 May 26
0
Kernel panic on 6.8 release with kernel-2.6.32-642.el6.x86_64
Hello Sorin,
Thursday, May 26, 2016, 1:58:29 PM, you wrote:
> Hi,
> Of the four machines tested, two failed with a kernel panic.
> At the time, I just rebooted to a previous kernel, as a quick fix.
> I found some of the issues you list already.
> I've run the CR-updates on a few test-machines since they became available
> and have had no problem. Weird...
> I've
2015 Aug 08
0
CentOS-announce Digest, Vol 126, Issue 3
Send CentOS-announce mailing list submissions to
centos-announce at centos.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.centos.org/mailman/listinfo/centos-announce
or, via email, send a message with subject or body 'help' to
centos-announce-request at centos.org
You can reach the person managing the list at
centos-announce-owner at centos.org
When
2015 Nov 27
4
at Japanese ReleaseNote6.7 , miss-writing is found.
At "CentOS 6.7 Release Notes"s Japanese-translated-version ("???
(ja)"), "CentOS 6.7 ???????"(https://wiki.centos.org/Manuals
/ReleaseNotes/CentOS6.7 /Japanese),
Miss-writring is exist.
At "9. ?????????" ( corresponding English version "9. How to
help and get help"),
?(miss-writring)????????????????Contribute???????
??? ?
2015 Nov 27
0
at Japanese ReleaseNote6.7 , miss-writing is found.
Hi Ooyama-san,
Thanks for your feedback. I fixed TYPO about your attention.
Could you confirm current page?
https://wiki.centos.org/Manuals/ReleaseNotes/CentOS6.7/Japanese
Best regards,
Taira
2015-11-27 20:49 GMT+09:00 Yosiyuki Ooyama <qqke6wd9k at apricot.ocn.ne.jp>:
> At "CentOS 6.7 Release Notes"s Japanese-translated-version ("???
> (ja)"), "CentOS 6.7
2016 May 26
2
Kernel panic on 6.8 release with kernel-2.6.32-642.el6.x86_64
> -----Original Message-----
> From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On
> Behalf Of Johnny Hughes
> Sent: den 26 maj 2016 12:39
> To: centos at centos.org
> Subject: Re: [CentOS] Kernel panic on 6.8 release with kernel-2.6.32-
> 642.el6.x86_64
>
> Did you see it in every case or just one case?
>
> That kernel has been out there
2015 Aug 07
2
6.7
I don't have CR enabled and a heap of available updates means CentOS 6.7
has been released or what?
Did I miss the announcement?
2016 May 26
2
Kernel panic on 6.8 release with kernel-2.6.32-642.el6.x86_64
> -----Original Message-----
> From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On
> Behalf Of Subscriber
> Sent: den 26 maj 2016 13:32
> To: CentOS mailing list <centos at centos.org>
> Subject: Re: [CentOS] Kernel panic on 6.8 release with kernel-2.6.32-
> 642.el6.x86_64
>
> Im just updated VM from 6.7 on 6.8 without problems. KVM
2016 Jun 28
0
The clang for centos6 are need GLIBC_2.14, but we only have GLIB 2.12 by default.
Yes, I believe it was built against centos 6.7. I wanted to build it
against an older release but couldn't quite bootstrap it without newer
libstdc++.
Sorry, it would be clearer if I'd have made the package name include
"centos6.7".
On Tue, Jun 28, 2016 at 11:43 AM, 罗勇刚(Yonggang Luo) <llvm-dev at lists.llvm.org
> wrote:
> [root at localhost
2015 Jul 30
0
why no recent bind update for CentOS 6?
On 07/30/2015 04:37 AM, Johnny Hughes wrote:
> On 07/29/2015 07:27 PM, Nathan Duehr wrote:
>>>
>>> On Jul 29, 2015, at 18:20, Nathan Duehr <denverpilot at me.com> wrote:
>>>
>>>> On Jul 28, 2015, at 18:48, Peter <peter at pajamian.dhs.org> wrote:
>>>>
>>>> On 07/29/2015 11:51 AM, Noam Bernstein wrote:
2015 Aug 07
0
6.7
On 08/07/2015 06:56 AM, Farkas Levente wrote:
> On 08/07/2015 01:04 PM, Johnny Hughes wrote:
>> 6.7 is there most places ... since we have more than 500 external
>> mirrors (right now 593) not all of them are updated. (looks like
>> 4% still are not completely updated)
>
> what about the src.rpms? it seems http://vault.centos.org/6.7/os/ and
>
2016 May 06
0
After restart, user's gnome autostart seems broken
Hello there,
CentOS6.7 64-bit up-to-date running on my laptop.. This night I had to
restart (did it properly). Since then, my ~/.config/autostart/ contains
some new broken .desktop files and /var/log/messages complains:
gnome-session[7280]: WARNING: Could not parse desktop file /home/wwp/.config/autostart/gnome-keyring-daemon.desktop: Key file does not have key 'Name'
2016 May 26
0
Kernel panic on 6.8 release with kernel-2.6.32-642.el6.x86_64
On 05/26/2016 06:49 AM, Sorin Srbu wrote:
> Content-Type: text/plain;
>
> charset="us-ascii"
>
> Content-Transfer-Encoding: 7bit
>
>
>> -----Original Message-----
>
>> From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On
>
>> Behalf Of Subscriber
>
>> Sent: den 26 maj 2016 13:32
>
>> To: CentOS
2015 Jul 30
4
why no recent bind update for CentOS 6?
On 07/29/2015 07:27 PM, Nathan Duehr wrote:
>>
>> On Jul 29, 2015, at 18:20, Nathan Duehr <denverpilot at me.com> wrote:
>>
>>> On Jul 28, 2015, at 18:48, Peter <peter at pajamian.dhs.org> wrote:
>>>
>>> On 07/29/2015 11:51 AM, Noam Bernstein wrote:
>>>> Hi CentOS developers - I?ve been happily using CentOS for several
2015 Jul 30
0
why no recent bind update for CentOS 6?
> On Jul 30, 2015, at 03:37, Johnny Hughes <johnny at centos.org> wrote:
>
> Of course it makes sense. Those security updates are not released in a
> vacuum, and all the things they are built on/against also need to be
> released and installed for them to work.
>
> The source code for the ssecurity updates you are talking about are
> built against RHEL-6.7, not 6.6
2015 Jul 30
1
why no recent bind update for CentOS 6?
>
> On Jul 29, 2015, at 18:20, Nathan Duehr <denverpilot at me.com> wrote:
>
>> On Jul 28, 2015, at 18:48, Peter <peter at pajamian.dhs.org> wrote:
>>
>> On 07/29/2015 11:51 AM, Noam Bernstein wrote:
>>> Hi CentOS developers - I?ve been happily using CentOS for several
>>> years now, so thanks for all the good work. In the last week,
2016 May 17
2
Continuous Release repository RPMs now released
On 05/16/2016 04:02 PM, Wes James wrote:
> On Mon, May 16, 2016 at 12:47 PM, Johnny Hughes <johnny at centos.org> wrote:
>
>> The Continuous Release repository RPMs for CentOS-6.8 are now released.
>> It includes the following releases:
>>
>>
> This is the first time I've installed updates from CR. I did this on 6.7
> in virtualbox. When I reboot,