hi
builds from 2014 06 17 are now online, the entire tree is refreshed and livecd + livemedia-gnome and livemedia-kde are also available.
- KB
On 06/18/2014 01:37 AM, Karanbir Singh wrote:
hi
builds from 2014 06 17 are now online, the entire tree is refreshed and livecd + livemedia-gnome and livemedia-kde are also available.
There is a 'latest' symlink for the tree's at http://buildlogs.centos.org/centos/7/os/ - if anyone is using that, then make sure you are running 'yum distro-sync' often.
From the yum man page :
distribution-synchronization or distro-sync Synchronizes the installed package set with the latest packages available, this is done by either obsoleting, upgrading or down- grading as appropriate. This will "normally" do the same thing as the upgrade command however if you have the package FOO installed at version 4, and the latest available is only version 3, then this command will downgrade FOO to version 3.
This command does not perform operations on groups, local pack- ages or negative selections.
- KB
On 18/06/14 12:55, Karanbir Singh wrote:
On 06/18/2014 01:37 AM, Karanbir Singh wrote:
hi
builds from 2014 06 17 are now online, the entire tree is refreshed and livecd + livemedia-gnome and livemedia-kde are also available.
There is a 'latest' symlink for the tree's at http://buildlogs.centos.org/centos/7/os/ - if anyone is using that, then make sure you are running 'yum distro-sync' often.
From the yum man page :
distribution-synchronization or distro-sync Synchronizes the installed package set with the latest packages available, this is done by either obsoleting, upgrading or down- grading as appropriate. This will "normally" do the same thing as the upgrade command however if you have the package FOO installed at version 4, and the latest available is only version 3, then this command will downgrade FOO to version 3.
This command does not perform operations on groups, local pack- ages or negative selections.
Just to add that , to play it nice and safe, it would even be better to force reinstall of packages using the same N-E-V-R, but with different checksums (to be sure that you're really using the packages from the latest tree) So "yum distro-sync full" is somewhat preferred :
"If you give the optional argument "full", then the command will also reinstall packages where the install checksum and the available checksum do not match. And remove old packages (can be used to sync. rpmdb versions). The optional argument "different" can be used to specify the default operation."
Happy testing ! and don't forget the Feedback please ;-)
On Wed, Jun 18, 2014 at 01:49:05PM +0200, Fabian Arrotin wrote:
On 18/06/14 12:55, Karanbir Singh wrote:
On 06/18/2014 01:37 AM, Karanbir Singh wrote:
hi
builds from 2014 06 17 are now online, the entire tree is refreshed and livecd + livemedia-gnome and livemedia-kde are also available.
There is a 'latest' symlink for the tree's at http://buildlogs.centos.org/centos/7/os/ - if anyone is using that, then make sure you are running 'yum distro-sync' often.
OK, dumb question: I'm running the bootinst iso (in virtualbox) that I downloaded yesterday. no matter what I enter in "installation source" it tells me it's had an error. What exactly am I supposed to put there?
I've tried http://buildlogs.centos.org/centos/7/os/x86_64-latest/ and the same without the trailing slash. I've trimmed off nodes from the end one at a time, and none of those settings has worked.
Someone gimme a smack upside the head, please?
18.6.2014 22.09, Fred Smith kirjoitti:
On Wed, Jun 18, 2014 at 01:49:05PM +0200, Fabian Arrotin wrote:
On 18/06/14 12:55, Karanbir Singh wrote:
On 06/18/2014 01:37 AM, Karanbir Singh wrote:
hi
builds from 2014 06 17 are now online, the entire tree is refreshed and livecd + livemedia-gnome and livemedia-kde are also available.
There is a 'latest' symlink for the tree's at http://buildlogs.centos.org/centos/7/os/ - if anyone is using that, then make sure you are running 'yum distro-sync' often.
OK, dumb question: I'm running the bootinst iso (in virtualbox) that I downloaded yesterday. no matter what I enter in "installation source" it tells me it's had an error. What exactly am I supposed to put there?
I've tried http://buildlogs.centos.org/centos/7/os/x86_64-latest/ and the same without the trailing slash. I've trimmed off nodes from the end one at a time, and none of those settings has worked.
Someone gimme a smack upside the head, please?
You will need to set up networking prior to selecting the installation source.
I consider it a UI glitch that the networking setup is the last item on the setup page, even though a working network connection may already be needed for the prior steps.
Networking is also needed for setting the time with NTP (in the timezone settings screen), and it also "mysteriously" fails if networking has not been set up yet.
On Wed, Jun 18, 2014 at 10:14:16PM +0300, Anssi Johansson wrote:
18.6.2014 22.09, Fred Smith kirjoitti:
On Wed, Jun 18, 2014 at 01:49:05PM +0200, Fabian Arrotin wrote:
On 18/06/14 12:55, Karanbir Singh wrote:
On 06/18/2014 01:37 AM, Karanbir Singh wrote:
hi
builds from 2014 06 17 are now online, the entire tree is refreshed and livecd + livemedia-gnome and livemedia-kde are also available.
There is a 'latest' symlink for the tree's at http://buildlogs.centos.org/centos/7/os/ - if anyone is using that, then make sure you are running 'yum distro-sync' often.
OK, dumb question: I'm running the bootinst iso (in virtualbox) that I downloaded yesterday. no matter what I enter in "installation source" it tells me it's had an error. What exactly am I supposed to put there?
I've tried http://buildlogs.centos.org/centos/7/os/x86_64-latest/ and the same without the trailing slash. I've trimmed off nodes from the end one at a time, and none of those settings has worked.
Someone gimme a smack upside the head, please?
You will need to set up networking prior to selecting the installation source.
AHA! (DUH! that's SO obvious, how did I miss that?)
thanks!
I consider it a UI glitch that the networking setup is the last item on the setup page, even though a working network connection may already be needed for the prior steps.
Networking is also needed for setting the time with NTP (in the timezone settings screen), and it also "mysteriously" fails if networking has not been set up yet. _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org http://lists.centos.org/mailman/listinfo/centos-devel
On Wed, Jun 18, 2014 at 01:49:05PM +0200, Fabian Arrotin wrote:
On 18/06/14 12:55, Karanbir Singh wrote:
On 06/18/2014 01:37 AM, Karanbir Singh wrote:
hi
builds from 2014 06 17 are now online, the entire tree is refreshed and livecd + livemedia-gnome and livemedia-kde are also available.
There is a 'latest' symlink for the tree's at http://buildlogs.centos.org/centos/7/os/ - if anyone is using that, then make sure you are running 'yum distro-sync' often.
From the yum man page :
distribution-synchronization or distro-sync Synchronizes the installed package set with the latest packages available, this is done by either obsoleting, upgrading or down- grading as appropriate. This will "normally" do the same thing as the upgrade command however if you have the package FOO installed at version 4, and the latest available is only version 3, then this command will downgrade FOO to version 3.
This command does not perform operations on groups, local pack- ages or negative selections.Just to add that , to play it nice and safe, it would even be better to force reinstall of packages using the same N-E-V-R, but with different checksums (to be sure that you're really using the packages from the latest tree) So "yum distro-sync full" is somewhat preferred :
I just tried "yum distro-sync full" and I get an error about there not being a kernel to delete. but if I ran without the "full", I got a bunch of updates.
On 06/25/2014 12:38 PM, Fred Smith wrote:
On Wed, Jun 18, 2014 at 01:49:05PM +0200, Fabian Arrotin wrote:
On 18/06/14 12:55, Karanbir Singh wrote:
On 06/18/2014 01:37 AM, Karanbir Singh wrote:
hi
builds from 2014 06 17 are now online, the entire tree is refreshed and livecd + livemedia-gnome and livemedia-kde are also available.
There is a 'latest' symlink for the tree's at http://buildlogs.centos.org/centos/7/os/ - if anyone is using that, then make sure you are running 'yum distro-sync' often.
From the yum man page :
distribution-synchronization or distro-sync Synchronizes the installed package set with the latest packages available, this is done by either obsoleting, upgrading or down- grading as appropriate. This will "normally" do the same thing as the upgrade command however if you have the package FOO installed at version 4, and the latest available is only version 3, then this command will downgrade FOO to version 3.
This command does not perform operations on groups, local pack- ages or negative selections.Just to add that , to play it nice and safe, it would even be better to force reinstall of packages using the same N-E-V-R, but with different checksums (to be sure that you're really using the packages from the latest tree) So "yum distro-sync full" is somewhat preferred :
I just tried "yum distro-sync full" and I get an error about there not being a kernel to delete. but if I ran without the "full", I got a bunch of updates.
You may have to 'yum reinstall kernel' manually ... it does not like to update that.
On Wed, Jun 25, 2014 at 12:44:12PM -0500, Johnny Hughes wrote:
On 06/25/2014 12:38 PM, Fred Smith wrote:
On Wed, Jun 18, 2014 at 01:49:05PM +0200, Fabian Arrotin wrote:
On 18/06/14 12:55, Karanbir Singh wrote:
On 06/18/2014 01:37 AM, Karanbir Singh wrote:
hi
builds from 2014 06 17 are now online, the entire tree is refreshed and livecd + livemedia-gnome and livemedia-kde are also available.
There is a 'latest' symlink for the tree's at http://buildlogs.centos.org/centos/7/os/ - if anyone is using that, then make sure you are running 'yum distro-sync' often.
From the yum man page :
distribution-synchronization or distro-sync Synchronizes the installed package set with the latest packages available, this is done by either obsoleting, upgrading or down- grading as appropriate. This will "normally" do the same thing as the upgrade command however if you have the package FOO installed at version 4, and the latest available is only version 3, then this command will downgrade FOO to version 3.
This command does not perform operations on groups, local pack- ages or negative selections.Just to add that , to play it nice and safe, it would even be better to force reinstall of packages using the same N-E-V-R, but with different checksums (to be sure that you're really using the packages from the latest tree) So "yum distro-sync full" is somewhat preferred :
I just tried "yum distro-sync full" and I get an error about there not being a kernel to delete. but if I ran without the "full", I got a bunch of updates.
You may have to 'yum reinstall kernel' manually ... it does not like to update that.
# yum reinstall kernel Loaded plugins: langpacks Skipping the running kernel: kernel-3.10.0-123.el7.x86_64 Error: Nothing to do
Greetings,
----- Original Message -----
# yum reinstall kernel Loaded plugins: langpacks Skipping the running kernel: kernel-3.10.0-123.el7.x86_64 Error: Nothing to do
The issue is the kernel you are running/have installed is newer than the one provided by the "yum distro-sync full" operation and updating to older kernels isn't something it was designed to do. You can get past that by manually installing the older kernel by referring to it by the complete name including version number... and then rebooting making sure to boot the older kernel. When the undesired kernel is no longer the one that is running, you can remove it... and a "yum distro-sync full" should be happy.
TYL,
On Wed, Jun 25, 2014 at 03:48:31PM -0600, Scott Dowdle wrote:
Greetings,
----- Original Message -----
# yum reinstall kernel Loaded plugins: langpacks Skipping the running kernel: kernel-3.10.0-123.el7.x86_64 Error: Nothing to do
The issue is the kernel you are running/have installed is newer than the one provided by the "yum distro-sync full" operation and updating to older kernels isn't something it was designed to do. You can get past that by manually installing the older kernel by referring to it by the complete name including version number... and then rebooting making sure to boot the older kernel. When the undesired kernel is no longer the one that is running, you can remove it... and a "yum distro-sync full" should be happy.
So, if I'm using a kernel I got from the 7-RC (the -latest) "repo", how could it have gotten out of sync?
Looking at "yum list available" to see what kernel is on the "repo", I see it's 3.10.0-123 which is the same as what's installed.
Seems like a "catch-22" wherein if you have only one kernel on the box, you can't replace it because it's the only kernel on the box. or something of that ilk.
On 06/25/2014 11:09 PM, Fred Smith wrote:
On Wed, Jun 25, 2014 at 03:48:31PM -0600, Scott Dowdle wrote:
Greetings,
----- Original Message -----
# yum reinstall kernel Loaded plugins: langpacks Skipping the running kernel: kernel-3.10.0-123.el7.x86_64 Error: Nothing to do
The issue is the kernel you are running/have installed is newer than the one provided by the "yum distro-sync full" operation and updating to older kernels isn't something it was designed to do. You can get past that by manually installing the older kernel by referring to it by the complete name including version number... and then rebooting making sure to boot the older kernel. When the undesired kernel is no longer the one that is running, you can remove it... and a "yum distro-sync full" should be happy.
So, if I'm using a kernel I got from the 7-RC (the -latest) "repo", how could it have gotten out of sync?
Looking at "yum list available" to see what kernel is on the "repo", I see it's 3.10.0-123 which is the same as what's installed.
Seems like a "catch-22" wherein if you have only one kernel on the box, you can't replace it because it's the only kernel on the box. or something of that ilk.
yum wont replace the kernel you are currently running, that is indeed an issue and the reason you hit this is that the new kernel in the latest build from today is indeed different and has different code inside there - but its the same name-version-release
you just hit a classic CentOS QA issue - and this is also why we go out of our way to be pedantic about not-for-users.
your only way to get the new kernel is to reinstall the machine, or to find something else somewhere ( plus kernel ? ) boot it, replace the distro kernel, boot back and hope for the best.
On Wed, Jun 25, 2014 at 11:14:31PM +0100, Karanbir Singh wrote:
On 06/25/2014 11:09 PM, Fred Smith wrote:
On Wed, Jun 25, 2014 at 03:48:31PM -0600, Scott Dowdle wrote:
Greetings,
----- Original Message -----
# yum reinstall kernel Loaded plugins: langpacks Skipping the running kernel: kernel-3.10.0-123.el7.x86_64 Error: Nothing to do
The issue is the kernel you are running/have installed is newer than the one provided by the "yum distro-sync full" operation and updating to older kernels isn't something it was designed to do. You can get past that by manually installing the older kernel by referring to it by the complete name including version number... and then rebooting making sure to boot the older kernel. When the undesired kernel is no longer the one that is running, you can remove it... and a "yum distro-sync full" should be happy.
So, if I'm using a kernel I got from the 7-RC (the -latest) "repo", how could it have gotten out of sync?
Looking at "yum list available" to see what kernel is on the "repo", I see it's 3.10.0-123 which is the same as what's installed.
Seems like a "catch-22" wherein if you have only one kernel on the box, you can't replace it because it's the only kernel on the box. or something of that ilk.
yum wont replace the kernel you are currently running, that is indeed an issue and the reason you hit this is that the new kernel in the latest build from today is indeed different and has different code inside there
- but its the same name-version-release
you just hit a classic CentOS QA issue - and this is also why we go out of our way to be pedantic about not-for-users.
your only way to get the new kernel is to reinstall the machine, or to find something else somewhere ( plus kernel ? ) boot it, replace the distro kernel, boot back and hope for the best.
OK, it's no big deal to reinstall, it's just a VM, created for the purpose of beating on C7.
thanks!
Greetings,
----- Original Message -----
OK, it's no big deal to reinstall, it's just a VM, created for the purpose of beating on C7.
The RHEL 7 install media has the initial kernel release and they have released two updates since then. The second one just came out today. Anyway, I was mistakenly under the impression that the first CentOS build was based on the first update... and that they had refreshed with the install media kernel... but indeed both the original and the current are the same version (as KS pointed out) which makes it virtually impossible to replace it.
I tried some dangerous package manager manipulations like the following:
yumdownloader kernel ; rpm -e --justdb --nodeps kernel ; rpm -ivh kernel*.rpm ; grub2-mkconfig -o /boot/grub2/grub.cfg ; systemctl reboot
It came back up just fine... but "yum clean all ; yum distro-sync full" still complained about it. Not sure why but yeah, do a reinstall. :)
Or you could wait until an updated kernel package comes out and upgrade to it... but that'd probably be after GA and at that point you'd want the REAL GA release anyway.
TYL,
-
Anssi Johansson -
Fabian Arrotin -
Fred Smith -
Johnny Hughes -
Karanbir Singh -
Scott Dowdle