Hi everyone!
It seems that the latest released version of qemu-kvm-ev is qemu-kvm-ev-2.3.0-31.el7_2.21.1 based on the following:
https://cbs.centos.org/koji/packageinfo?packageID=539
However, our systems are refusing to update to that package because qemu-kvm-ev-2.3.0-31.el7.16.1 is installed. I believe the 16.1 is making it seem that it is newer than 2.21.1 (16 > 2). As a result, we're unable to update and it seems that the latest package covers 2 CVE's, to which this one doesn't.
Is this something that was done on purpose to control releases or is this a bug?
Thanks, Mohammed
On 12/11/16 10:02, Mohammed Naser wrote:
It seems that the latest released version of qemu-kvm-ev is qemu-kvm-ev-2.3.0-31.el7_2.21.1 based on the following:
https://cbs.centos.org/koji/packageinfo?packageID=539
However, our systems are refusing to update to that package because qemu-kvm-ev-2.3.0-31.el7.16.1 is installed. I believe the 16.1 is making it seem that it is newer than 2.21.1 (16 > 2). As a result, we're unable to update and it seems that the latest package covers 2 CVE's, to which this one doesn't.
No, it sorts properly: $ printf '%s\n' 2.3.0-31.el7_2.21.1 2.3.0-31.el7.16.1 | sort -V 2.3.0-31.el7.16.1 2.3.0-31.el7_2.21.1
Is this something that was done on purpose to control releases or is this a bug?
Neither, you likely do not have centos-release-qemu-ev installed, have disabled the repo or are using an out of date mirror.
Peter
On 11/11/2016 11:20 PM, Peter wrote:
On 12/11/16 10:02, Mohammed Naser wrote:
It seems that the latest released version of qemu-kvm-ev is qemu-kvm-ev-2.3.0-31.el7_2.21.1 based on the following:
https://cbs.centos.org/koji/packageinfo?packageID=539
However, our systems are refusing to update to that package because qemu-kvm-ev-2.3.0-31.el7.16.1 is installed. I believe the 16.1 is making it seem that it is newer than 2.21.1 (16 > 2). As a result, we're unable to update and it seems that the latest package covers 2 CVE's, to which this one doesn't.
No, it sorts properly: $ printf '%s\n' 2.3.0-31.el7_2.21.1 2.3.0-31.el7.16.1 | sort -V 2.3.0-31.el7.16.1 2.3.0-31.el7_2.21.1
RPM has a pretty elaborate sorting mechanism it uses when comparing versions and releases, which won't always match what "sort -V" thinks.
Using the "rpmdev-vercmp" utility from the rpmdevtools package:
$ rpmdev-vercmp 0 2.3.0 31.el7.16.1 0 2.3.0 31.el7_2.21.1 0:2.3.0-31.el7.16.1 > 0:2.3.0-31.el7_2.21.1
So the installed version appears to be newer than the "el7_2" version.
Following looks to be a fairly good write up of how the version comparison works:
http://blog.jasonantman.com/2014/07/how-yum-and-rpm-compare-versions/
-Greg
Il 11/Nov/2016 22:03, "Mohammed Naser" mnaser@vexxhost.com ha scritto:
Hi everyone!
It seems that the latest released version of qemu-kvm-ev is qemu-kvm-ev-2.3.0-31.el7_2.21.1 based on the following:
https://cbs.centos.org/koji/packageinfo?packageID=539
However, our systems are refusing to update to that package because qemu-kvm-ev-2.3.0-31.el7.16.1 is installed. I believe the 16.1 is making it seem that it is newer than 2.21.1 (16 > 2).
Looks like dist tag is not considered in version computation. 21.1 is higher than 16.1 but el7 is considered higher than el7_2. Just to be sure, please try yum clean metadata, and then yum distro-sync.
As a result,
we're unable to update and it seems that the latest package covers 2 CVE's, to which this one doesn't.
Is this something that was done on purpose to control releases or is this
a bug?
Thanks, Mohammed
-- Mohammed Naser — vexxhost
D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser@vexxhost.com W. http://vexxhost.com _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 11/12/2016 01:27 AM, Sandro Bonazzola wrote:
Il 11/Nov/2016 22:03, "Mohammed Naser" <mnaser@vexxhost.com mailto:mnaser@vexxhost.com> ha scritto:
Hi everyone!
It seems that the latest released version of qemu-kvm-ev is qemu-kvm-ev-2.3.0-31.el7_2.21.1 based on the following:
https://cbs.centos.org/koji/packageinfo?packageID=539
However, our systems are refusing to update to that package because qemu-kvm-ev-2.3.0-31.el7.16.1 is installed. I believe the 16.1 is making it seem that it is newer than 2.21.1 (16 > 2).
Looks like dist tag is not considered in version computation. 21.1 is higher than 16.1 but el7 is considered higher than el7_2. Just to be sure, please try yum clean metadata, and then yum distro-sync.
I can confirm this behavior here. In fact, it looks like we've missed two updates; el7_2.16.1 was released the day after el7.16.1 was, and that one didn't update my install, either. In checking, it appears that both have an epoch of 10.
A yum distro-sync does not offer to reinstall qemu-$subpackage-ev for me, even after yum clean metadata or yum clean all.
On Sat, Nov 12, 2016 at 4:37 PM, Lamar Owen lowen@pari.edu wrote:
On 11/12/2016 01:27 AM, Sandro Bonazzola wrote:
Il 11/Nov/2016 22:03, "Mohammed Naser" <mnaser@vexxhost.com <mailto:
mnaser@vexxhost.com>> ha scritto:
Hi everyone!
It seems that the latest released version of qemu-kvm-ev is qemu-kvm-ev-2.3.0-31.el7_2.21.1 based on the following:
https://cbs.centos.org/koji/packageinfo?packageID=539
However, our systems are refusing to update to that package because qemu-kvm-ev-2.3.0-31.el7.16.1 is installed. I believe the 16.1 is making it seem that it is newer than 2.21.1 (16 > 2).
Looks like dist tag is not considered in version computation. 21.1 is higher than 16.1 but el7 is considered higher than el7_2. Just to be sure, please try yum clean metadata, and then yum distro-sync.
I can confirm this behavior here. In fact, it looks like we've missed
two updates; el7_2.16.1 was released the day after el7.16.1 was, and that one didn't update my install, either. In checking, it appears that both have an epoch of 10.
A yum distro-sync does not offer to reinstall qemu-$subpackage-ev for me, even after yum clean metadata or yum clean all.
karanbir any chance we can get the offending package removed from the repository? So at least rpm -Uvh --force to the newer release will work and yum won't try to downgrade it.
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 15/11/16 13:38, Sandro Bonazzola wrote:
On Sat, Nov 12, 2016 at 4:37 PM, Lamar Owen <lowen@pari.edu mailto:lowen@pari.edu> wrote:
On 11/12/2016 01:27 AM, Sandro Bonazzola wrote: Il 11/Nov/2016 22:03, "Mohammed Naser" <mnaser@vexxhost.com <mailto:mnaser@vexxhost.com> <mailto:mnaser@vexxhost.com <mailto:mnaser@vexxhost.com>>> ha scritto: > > Hi everyone! > > It seems that the latest released version of qemu-kvm-ev is > qemu-kvm-ev-2.3.0-31.el7_2.21.1 based on the following: > > https://cbs.centos.org/koji/packageinfo?packageID=539 <https://cbs.centos.org/koji/packageinfo?packageID=539> > > However, our systems are refusing to update to that package because > qemu-kvm-ev-2.3.0-31.el7.16.1 is installed. I believe the 16.1 is > making it seem that it is newer than 2.21.1 (16 > 2). Looks like dist tag is not considered in version computation. 21.1 is higher than 16.1 but el7 is considered higher than el7_2. Just to be sure, please try yum clean metadata, and then yum distro-sync. I can confirm this behavior here. In fact, it looks like we've missed two updates; el7_2.16.1 was released the day after el7.16.1 was, and that one didn't update my install, either. In checking, it appears that both have an epoch of 10. A yum distro-sync does not offer to reinstall qemu-$subpackage-ev for me, even after yum clean metadata or yum clean all.
karanbir any chance we can get the offending package removed from the repository? So at least rpm -Uvh --force to the newer release will work and yum won't try to downgrade it.
if we were to try and resolve this without removing rpms, what would that solution look like ?
Am 15.11.2016 um 15:31 schrieb Karanbir Singh mail-lists@karan.org:
On 15/11/16 13:38, Sandro Bonazzola wrote:
Looks like dist tag is not considered in version computation. 21.1 is higher than 16.1 but el7 is considered higher than el7_2. Just to be sure, please try yum clean metadata, and then yum distro-sync.
I can confirm this behavior here. In fact, it looks like we've missed two updates; el7_2.16.1 was released the day after el7.16.1 was, and that one didn't update my install, either. In checking, it appears that both have an epoch of 10.
A yum distro-sync does not offer to reinstall qemu-$subpackage-ev for me, even after yum clean metadata or yum clean all.
karanbir any chance we can get the offending package removed from the repository? So at least rpm -Uvh --force to the newer release will work and yum won't try to downgrade it.
if we were to try and resolve this without removing rpms, what would that solution look like ?
qemu-kvm-ev-2.1.2-23.el7_1.8.1.x86_64.rpm 23-Oct-2015 11:19 1.9M qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64.rpm 08-Aug-2016 17:36 2.1M qemu-kvm-ev-2.3.0-31.el7_2.7.1.x86_64.rpm 03-Feb-2016 16:51 2.1M qemu-kvm-ev-2.3.0-31.el7_2.10.1.x86_64.rpm 14-Apr-2016 12:16 2.1M qemu-kvm-ev-2.3.0-31.el7_2.16.1.x86_64.rpm 09-Aug-2016 12:53 2.1M qemu-kvm-ev-2.3.0-31.el7_2.21.1.x86_64.rpm 24-Aug-2016 13:40 2.1M
are this packages intentional (dist tag diff)?
qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64.rpm 08-Aug-2016 17:36 2.1M qemu-kvm-ev-2.3.0-31.el7_2.16.1.x86_64.rpm 09-Aug-2016 12:53 2.1M
-- LF
On 15/11/16 16:16, Leon Fauster wrote:
Am 15.11.2016 um 15:31 schrieb Karanbir Singh mail-lists@karan.org:
On 15/11/16 13:38, Sandro Bonazzola wrote:
qemu-kvm-ev-2.1.2-23.el7_1.8.1.x86_64.rpm 23-Oct-2015 11:19 1.9M qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64.rpm 08-Aug-2016 17:36 2.1M qemu-kvm-ev-2.3.0-31.el7_2.7.1.x86_64.rpm 03-Feb-2016 16:51 2.1M qemu-kvm-ev-2.3.0-31.el7_2.10.1.x86_64.rpm 14-Apr-2016 12:16 2.1M qemu-kvm-ev-2.3.0-31.el7_2.16.1.x86_64.rpm 09-Aug-2016 12:53 2.1M qemu-kvm-ev-2.3.0-31.el7_2.21.1.x86_64.rpm 24-Aug-2016 13:40 2.1M
are this packages intentional (dist tag diff)?
qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64.rpm 08-Aug-2016 17:36 2.1M qemu-kvm-ev-2.3.0-31.el7_2.16.1.x86_64.rpm 09-Aug-2016 12:53 2.1M
That looks to me like the
qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64.rpm 08-Aug-2016 17:36 2.1M
was wrongly named and was then rereleased the following day with the correct one as
qemu-kvm-ev-2.3.0-31.el7_2.16.1.x86_64.rpm 09-Aug-2016 12:53 2.1M
Trevor
Hi,
That's exactly what I guessed that the issue was, because the RPMs seem to match (in terms of changelog at least)
Thanks Mohammed
On Tue, Nov 15, 2016 at 11:23 AM, Trevor Hemsley trevor.hemsley@ntlworld.com wrote:
On 15/11/16 16:16, Leon Fauster wrote:
Am 15.11.2016 um 15:31 schrieb Karanbir Singh mail-lists@karan.org:
On 15/11/16 13:38, Sandro Bonazzola wrote:
qemu-kvm-ev-2.1.2-23.el7_1.8.1.x86_64.rpm 23-Oct-2015 11:19 1.9M qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64.rpm 08-Aug-2016 17:36 2.1M qemu-kvm-ev-2.3.0-31.el7_2.7.1.x86_64.rpm 03-Feb-2016 16:51 2.1M qemu-kvm-ev-2.3.0-31.el7_2.10.1.x86_64.rpm 14-Apr-2016 12:16 2.1M qemu-kvm-ev-2.3.0-31.el7_2.16.1.x86_64.rpm 09-Aug-2016 12:53 2.1M qemu-kvm-ev-2.3.0-31.el7_2.21.1.x86_64.rpm 24-Aug-2016 13:40 2.1M
are this packages intentional (dist tag diff)?
qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64.rpm 08-Aug-2016 17:36 2.1M qemu-kvm-ev-2.3.0-31.el7_2.16.1.x86_64.rpm 09-Aug-2016 12:53 2.1M
That looks to me like the
qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64.rpm 08-Aug-2016 17:36 2.1M
was wrongly named and was then rereleased the following day with the correct one as
qemu-kvm-ev-2.3.0-31.el7_2.16.1.x86_64.rpm 09-Aug-2016 12:53 2.1M
Trevor _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Il 15/Nov/2016 18:23, "Trevor Hemsley" trevor.hemsley@ntlworld.com ha scritto:
On 15/11/16 16:16, Leon Fauster wrote:
Am 15.11.2016 um 15:31 schrieb Karanbir Singh mail-lists@karan.org:
On 15/11/16 13:38, Sandro Bonazzola wrote:
qemu-kvm-ev-2.1.2-23.el7_1.8.1.x86_64.rpm 23-Oct-2015 11:19
1.9M
qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64.rpm 08-Aug-2016 17:36
2.1M
qemu-kvm-ev-2.3.0-31.el7_2.7.1.x86_64.rpm 03-Feb-2016 16:51
2.1M
qemu-kvm-ev-2.3.0-31.el7_2.10.1.x86_64.rpm 14-Apr-2016 12:16
2.1M
qemu-kvm-ev-2.3.0-31.el7_2.16.1.x86_64.rpm 09-Aug-2016 12:53
2.1M
qemu-kvm-ev-2.3.0-31.el7_2.21.1.x86_64.rpm 24-Aug-2016 13:40
2.1M
are this packages intentional (dist tag diff)?
qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64.rpm 08-Aug-2016 17:36
2.1M
qemu-kvm-ev-2.3.0-31.el7_2.16.1.x86_64.rpm 09-Aug-2016 12:53
2.1M
That looks to me like the
qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64.rpm 08-Aug-2016 17:36
2.1M
was wrongly named and was then rereleased the following day with the correct one as
qemu-kvm-ev-2.3.0-31.el7_2.16.1.x86_64.rpm 09-Aug-2016 12:53
2.1M
Yes. That's right. And we didn't notice the upgrade issue.
Trevor _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Le 15/11/2016 à 18:40, Sandro Bonazzola a écrit :
Il 15/Nov/2016 18:23, "Trevor Hemsley" <trevor.hemsley@ntlworld.com mailto:trevor.hemsley@ntlworld.com> ha scritto:
On 15/11/16 16:16, Leon Fauster wrote:
Am 15.11.2016 um 15:31 schrieb Karanbir Singh
<mail-lists@karan.org mailto:mail-lists@karan.org>:
On 15/11/16 13:38, Sandro Bonazzola wrote:
qemu-kvm-ev-2.1.2-23.el7_1.8.1.x86_64.rpm 23-Oct-2015 11:19
1.9M
qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64.rpm 08-Aug-2016 17:36 2.1M qemu-kvm-ev-2.3.0-31.el7_2.7.1.x86_64.rpm 03-Feb-2016 16:51
2.1M
qemu-kvm-ev-2.3.0-31.el7_2.10.1.x86_64.rpm 14-Apr-2016 12:16
2.1M
qemu-kvm-ev-2.3.0-31.el7_2.16.1.x86_64.rpm 09-Aug-2016 12:53
2.1M
qemu-kvm-ev-2.3.0-31.el7_2.21.1.x86_64.rpm 24-Aug-2016 13:40
2.1M
are this packages intentional (dist tag diff)?
qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64.rpm 08-Aug-2016 17:36 2.1M qemu-kvm-ev-2.3.0-31.el7_2.16.1.x86_64.rpm 09-Aug-2016 12:53
2.1M
That looks to me like the
qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64.rpm 08-Aug-2016 17:36
2.1M
was wrongly named and was then rereleased the following day with the correct one as
qemu-kvm-ev-2.3.0-31.el7_2.16.1.x86_64.rpm 09-Aug-2016 12:53
2.1M
Yes. That's right. And we didn't notice the upgrade issue.
Can't you rebuild the qemu-kvm-ev-2.3.0-31.%{?dist}.21.1.src.rpm with the el7 tag or bump the 31.%{?dist}.21.1 version to 32.%{?dist}.21.1 to fix this issue ?
Jean-Marc
Trevor _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 11/15/2016 05:30 PM, Jean-Marc Liger wrote:
Le 15/11/2016 à 18:40, Sandro Bonazzola a écrit :
Yes. That's right. And we didn't notice the upgrade issue.
Can't you rebuild the qemu-kvm-ev-2.3.0-31.%{?dist}.21.1.src.rpm with the el7 tag or bump the 31.%{?dist}.21.1 version to 32.%{?dist}.21.1 to fix this issue ?
Totally unnecessary if the el7.16..... rpms are just simply removed from the repo. Use 'yum downgrade qemu-*-ev' to upgrade to the el7_2.21.1 set. It actually does work.
While that works, it will mean that it will require manual intervention and proper notification of everyone consuming the repos.
That could likely be difficult, especially if those are all CVEs.
Sent from my iPhone
On Nov 15, 2016, at 7:10 PM, Lamar Owen lowen@pari.edu wrote:
On 11/15/2016 05:30 PM, Jean-Marc Liger wrote:
Le 15/11/2016 à 18:40, Sandro Bonazzola a écrit :
Yes. That's right. And we didn't notice the upgrade issue.
Can't you rebuild the qemu-kvm-ev-2.3.0-31.%{?dist}.21.1.src.rpm with the el7 tag or bump the 31.%{?dist}.21.1 version to 32.%{?dist}.21.1 to fix this issue ?
Totally unnecessary if the el7.16..... rpms are just simply removed from the repo. Use 'yum downgrade qemu-*-ev' to upgrade to the el7_2.21.1 set. It actually does work.
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 16/11/16 03:31, Karanbir Singh wrote:
if we were to try and resolve this without removing rpms, what would that solution look like ?
I would suggest bumping to 2.3.0-31.0.el7_2.21.1
That will resolve the issue without making anyone do anything other than "yum update".
Peter
On Wed, Nov 16, 2016 at 5:22 AM, Peter peter@pajamian.dhs.org wrote:
On 16/11/16 03:31, Karanbir Singh wrote:
if we were to try and resolve this without removing rpms, what would that solution look like ?
I would suggest bumping to 2.3.0-31.0.el7_2.21.1
That will resolve the issue without making anyone do anything other than "yum update".
I think that 2.6.0 release coming with 7.3 will solve the issue anyway.
Peter _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 11/16/2016 01:29 AM, Sandro Bonazzola wrote:
I think that 2.6.0 release coming with 7.3 will solve the issue anyway.
Agreed. The cure might just be worse than the disease.
ETA on 2.6.0 in centos-qemu-ev?
Il 16/Nov/2016 16:04, "Lamar Owen" lowen@pari.edu ha scritto:
On 11/16/2016 01:29 AM, Sandro Bonazzola wrote:
I think that 2.6.0 release coming with 7.3 will solve the issue anyway.
Agreed. The cure might just be worse than the disease.
ETA on 2.6.0 in centos-qemu-ev?
As soon as 7.3 bits are in cbs and 7.3 ready to go ga.
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 16/11/16 21:19, Sandro Bonazzola wrote:
Il 16/Nov/2016 16:04, "Lamar Owen" <lowen@pari.edu mailto:lowen@pari.edu> ha scritto:
On 11/16/2016 01:29 AM, Sandro Bonazzola wrote:
I think that 2.6.0 release coming with 7.3 will solve the issue anyway.
Agreed. The cure might just be worse than the disease.
ETA on 2.6.0 in centos-qemu-ev?
As soon as 7.3 bits are in cbs and 7.3 ready to go ga.
is there something we can push in the interim to get over the immediate issue ? the 7.1611 CR content might not be there this week
On 17/11/16 23:26, Karanbir Singh wrote:
is there something we can push in the interim to get over the immediate issue ? the 7.1611 CR content might not be there this week
Repeating what I said a few messages back:
I would suggest bumping to 2.3.0-31.0.el7_2.21.1
That will resolve the issue without making anyone do anything other than "yum update".
Peter
On Thu, Nov 17, 2016 at 11:58 AM, Peter peter@pajamian.dhs.org wrote:
On 17/11/16 23:26, Karanbir Singh wrote:
is there something we can push in the interim to get over the immediate issue ? the 7.1611 CR content might not be there this week
Repeating what I said a few messages back:
I would suggest bumping to 2.3.0-31.0.el7_2.21.1
qemu-kvm-ev-2.3.0-31.0.el7_2.21.1 tagged for testing http://cbs.centos.org/koji/buildinfo?buildID=14508. It should land on http://buildlogs.centos.org/centos/7/virt/x86_64/kvm-common/ pretty soon.
That will resolve the issue without making anyone do anything other than "yum update".
Peter _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Nov 21, 2016, at 4:41 AM, Sandro Bonazzola sbonazzo@redhat.com wrote:
On Thu, Nov 17, 2016 at 11:58 AM, Peter <peter@pajamian.dhs.org mailto:peter@pajamian.dhs.org> wrote: On 17/11/16 23:26, Karanbir Singh wrote:
is there something we can push in the interim to get over the immediate issue ? the 7.1611 CR content might not be there this week
Repeating what I said a few messages back:
I would suggest bumping to 2.3.0-31.0.el7_2.21.1
qemu-kvm-ev-2.3.0-31.0.el7_2.21.1 tagged for testing http://cbs.centos.org/koji/buildinfo?buildID=14508 http://cbs.centos.org/koji/buildinfo?buildID=14508. It should land on http://buildlogs.centos.org/centos/7/virt/x86_64/kvm-common/ http://buildlogs.centos.org/centos/7/virt/x86_64/kvm-common/ pretty soon.
Thank you very much Sandro. I appreciate your help in resolving this issue.
That will resolve the issue without making anyone do anything other than "yum update".
Peter _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel https://lists.centos.org/mailman/listinfo/centos-devel
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com http://redhat.com/_______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Mon, Nov 21, 2016 at 2:36 PM, Mohammed Naser mnaser@vexxhost.com wrote:
On Nov 21, 2016, at 4:41 AM, Sandro Bonazzola sbonazzo@redhat.com wrote:
On Thu, Nov 17, 2016 at 11:58 AM, Peter peter@pajamian.dhs.org wrote:
On 17/11/16 23:26, Karanbir Singh wrote:
is there something we can push in the interim to get over the immediate issue ? the 7.1611 CR content might not be there this week
Repeating what I said a few messages back:
I would suggest bumping to 2.3.0-31.0.el7_2.21.1
qemu-kvm-ev-2.3.0-31.0.el7_2.21.1 tagged for testing http://cbs.centos.org/koji/buildinfo?buildID=14508. It should land on http://buildlogs.centos.org/centos/7/virt/x86_64/kvm- common/ pretty soon.
Thank you very much Sandro. I appreciate your help in resolving this issue.
Thanks, let me know if it works for you.
That will resolve the issue without making anyone do anything other than "yum update".
Peter _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Hi Sandro,
On Nov 21, 2016, at 9:16 AM, Sandro Bonazzola sbonazzo@redhat.com wrote:
On Mon, Nov 21, 2016 at 2:36 PM, Mohammed Naser <mnaser@vexxhost.com mailto:mnaser@vexxhost.com> wrote:
On Nov 21, 2016, at 4:41 AM, Sandro Bonazzola <sbonazzo@redhat.com mailto:sbonazzo@redhat.com> wrote:
On Thu, Nov 17, 2016 at 11:58 AM, Peter <peter@pajamian.dhs.org mailto:peter@pajamian.dhs.org> wrote: On 17/11/16 23:26, Karanbir Singh wrote:
is there something we can push in the interim to get over the immediate issue ? the 7.1611 CR content might not be there this week
Repeating what I said a few messages back:
I would suggest bumping to 2.3.0-31.0.el7_2.21.1
qemu-kvm-ev-2.3.0-31.0.el7_2.21.1 tagged for testing http://cbs.centos.org/koji/buildinfo?buildID=14508 http://cbs.centos.org/koji/buildinfo?buildID=14508. It should land on http://buildlogs.centos.org/centos/7/virt/x86_64/kvm-common/ http://buildlogs.centos.org/centos/7/virt/x86_64/kvm-common/ pretty soon.
Thank you very much Sandro. I appreciate your help in resolving this issue.
Thanks, let me know if it works for you.
I can confirm that it works. On a machine which currently has qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64 — running yum install qemu-kvm-ev tries to install qemu-kvm-ev-2.3.0-31.0.el7_2.21.1.x86_64
Thanks everyone in helping fix this.
That will resolve the issue without making anyone do anything other than "yum update".
Peter _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel https://lists.centos.org/mailman/listinfo/centos-devel
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com http://redhat.com/_______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel https://lists.centos.org/mailman/listinfo/centos-devel
CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel https://lists.centos.org/mailman/listinfo/centos-devel
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com http://redhat.com/_______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org mailto:CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel https://lists.centos.org/mailman/listinfo/centos-devel
On 11/17/2016 05:26 AM, Karanbir Singh wrote:
is there something we can push in the interim to get over the immediate issue ? the 7.1611 CR content might not be there this week
Honestly, it's been this way since August; what's one more week? If the faulty rpms can be deleted then those who want to get the new can get it with yum downgrade qemu-*-ev quickly, and a yum update won't blow it back away. But the most time needs to be spent on the new (7.1611) packages, not kludging around a single broken update.
Hi,
On 11/16/2016 04:22 AM, Peter wrote:
On 16/11/16 03:31, Karanbir Singh wrote:
if we were to try and resolve this without removing rpms, what would that solution look like ?
I would suggest bumping to 2.3.0-31.0.el7_2.21.1
That will resolve the issue without making anyone do anything other than "yum update".
I agree this is the best way to do it for users. It is transparent. NVR bump FTW.