similar to: Question on CR

Hi, what is the right way to deal with the new cr repository for centos 5 when you are running your own mirror. In particular the following statement I don't fully understand: - Once 5.7 is released, the 5.6/cr/ repositories will be removed ( they will not be available on vault.centos.org ) Christian.

On http://wiki.centos.org/AdditionalResources/Repositories/CR the link to a copy of 64 bit CR repo is not working. The link is: http://mirror.centos.org/centos/5.6/cr/x86_64/RPMS/centos-release-cr-5-6.el5.centos.1.x86_64.rpm and the error message is (obtained from trying two distinctly different IPs on two distinctively different ISP networks): "Not Found "The requested "URL

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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. All upstream repositories have been combined into one, to make it easier for end users to work with. This is just an

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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. All upstream repositories have been combined into one, to make it easier for end users to work with. This is just an

The CentOS-5.6 Continuous Release ( CR ) repository is now available on mirror.centos.org. This repository contains rpms to be included in the next CentOS-5.x release. Because these include security and bugfix updates, we strongly recommend everyone using CentOS-5 install and update their system using this repository. --------------------- Download and Install: Installing the CR repository

The CentOS-5.6 Continuous Release ( CR ) repository is now available on mirror.centos.org. This repository contains rpms to be included in the next CentOS-5.x release. Because these include security and bugfix updates, we strongly recommend everyone using CentOS-5 install and update their system using this repository. --------------------- Download and Install: Installing the CR repository

Hi all, I have a Dell server, CentOS 5.6 64 bits, on which I configured the CR repository. I just tried to update to 5.7, and had this error : # yum update .... http://mirror.centos.org/centos/5/cr/x86_64/repodata/filelists.sqlite.bz2: [Errno 14] HTTP Error 404: Not Found Trying other mirror. Error: failure: repodata/filelists.sqlite.bz2 from cr: [Errno 256] No more mirrors to try. You could

All, Has anyone else had a problem with the CR repo on a 6.4 or 6.5 system? I have a test VM that has the CentOS6 CR repo enabled and it recently (well a week or so) started having dependency problems. It's choking on dependencies for ca-cerfificates. Obviously there aren't any CR packages yet for 6.5 so a zero package count and empty directory on the mirror [0] are legitimate. But

Hello Is anyone else having problems on 5.6 using the new rsync from the CR repo I have only managed to get rsync (called from the cli) working again after downgrading it to the previous 2.x release as the newer version was just spitting out the ssh usage information and failing. This server is stock i386 with just the CR as an extra repo. regards mike

As part of the CR process ( https://wiki.centos.org/AdditionalResources/Repositories/CR ), the following updates were done and are included in the CentOS base ( os/ ) repository for CentOS Linux 7.6.1810. https://lists.centos.org/pipermail/centos-cr-announce/2018-November/thread.html https://lists.centos.org/pipermail/centos-cr-announce/2018-December/thread.html There was an issue with the

As part of the CR process ( https://wiki.centos.org/AdditionalResources/Repositories/CR ), the following updates were done and are included in the CentOS base ( os/ ) repository for CentOS Linux 7.6.1810. https://lists.centos.org/pipermail/centos-cr-announce/2018-November/thread.html https://lists.centos.org/pipermail/centos-cr-announce/2018-December/thread.html There was an issue with the

Dear list, I'm currently trying to use the rms package to get predicted ordinal responses from a conditional ratio model. As you will see below, my model seems to fit well to the data, however, I'm having trouble getting predicted mean (or fitted) ordinal response values using the predict function. I have a feeling I'm missing something simple, however I haven't been able to

> Am 03.12.2018 um 11:14 schrieb John Hodrien <J.H.Hodrien at leeds.ac.uk>: > > On Mon, 3 Dec 2018, Simon Matter wrote: > >>> Le 03/12/2018 ? 06:25, Rob Kampen a ?crit : >>>> I enabled the CR repo and did the yum update. Some 800+ rpms were >>>> offered and all seemed to resolve depenancies OK, so yes it was >>>> started. The updates

I get: Failed to download prestodelta for repository cr: [Errno 256] No more mirrors to try. java-1.8.0-openjdk-1.8.0.111-2 FAILED http://mirror.centos.org/centos/7/cr/x86_64/Packages/java-1.8.0-openjdk-1.8.0.111-2.b15.el7_3.x86_64.rpm: [Errno 14] HTTP Error 404 - Not Found Trying other mirror. java-1.8.0-openjdk-devel-1.8.0 FAILED

I see the two distribution points for each release, they seem very alike, what is the difference? -Ross

We should have the CR packages, that will eventually be turned into the full 6.8 point release and ISO set, to the QA team today for testing. I expect that it will take 1 to 2 days in QA and then those will be ready for release into the 6.7/cr/ repository. That means that no later than Monday, May 16th (and maybe as early as sometime within the next 24 hours), the CR packages, including the

On 03/12/2018 11:14, John Hodrien wrote: > On Mon, 3 Dec 2018, Simon Matter wrote: > >>> Le 03/12/2018 ? 06:25, Rob Kampen a ?crit : >>>> I enabled the CR repo and did the yum update. Some 800+ rpms were >>>> offered and all seemed to resolve depenancies OK, so yes it was >>>> started. The updates completed and all looked good, until the reboot.

> Le 03/12/2018 ? 06:25, Rob Kampen a ?crit : >> I enabled the CR repo and did the yum update. Some 800+ rpms were >> offered and all seemed to resolve depenancies OK, so yes it was >> started. The updates completed and all looked good, until the reboot. >> > > I got a similar disaster here. I guess the lesson to be learned is that > CR is nice to have on

I did the update from CR, and have some pretty serious issues.? Until I blew away (by mv to a different name) the .local and .config directory trees, I couldn't log in to GNOME at all.? After doing that, I can log in, but if I do any actual work, GNOME crashes, and abrt-cli from root in vc 2 tells me that gnome-shell got a SIGSEGV.?I figure all of the updates aren't in CR yet, so I'm

C6 with CR x86_64 Third time when trying to install a packet I get: yum install samba [...] --> Finished Dependency Resolution Error: Package: glibc-2.12-1.7.el6_0.5.i686 (updates) Requires: glibc-common = 2.12-1.7.el6_0.5 Installed: glibc-common-2.12-1.25.el6_1.3.x86_64 (@cr) glibc-common = 2.12-1.25.el6_1.3 Available: