Karanbir Singh wrote:>if we were to try and resolve this without >removing rpms, what would
that solution look like ?
Increment epoch. Almost as tasty as removing rpms.
On Tue, Nov 15, 2016 at 5:20 PM, Lamar Owen lowen@pari.edu wrote:
Karanbir Singh wrote:
if we were to try and resolve this without >removing rpms, what would that solution look like ?
Increment epoch. Almost as tasty as removing rpms.
incrementing epoch will cause a chain of other issues so I don't think it's the good way to go here.
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Hi guys,
There was part of conversation "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." You can imagine that next time same situation will occur, but with incremented epoch it will be even more broken.
Sincerely Alex
On 11/15/2016 04:28 PM, Sandro Bonazzola wrote:
On Tue, Nov 15, 2016 at 5:20 PM, Lamar Owen <lowen@pari.edu mailto:lowen@pari.edu> wrote:
Karanbir Singh wrote: >if we were to try and resolve this without >removing rpms, what would >that solution look like ? Increment epoch. Almost as tasty as removing rpms.
incrementing epoch will cause a chain of other issues so I don't think it's the good way to go here.
_______________________________________________ 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 15/11/16 15:35, aleksander.baranowski wrote:
Hi guys,
There was part of conversation "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." You can imagine that next time same situation will occur, but with incremented epoch it will be even more broken.
Sincerely Alex
On 11/15/2016 04:28 PM, Sandro Bonazzola wrote:
On Tue, Nov 15, 2016 at 5:20 PM, Lamar Owen <lowen@pari.edu mailto:lowen@pari.edu> wrote:
Karanbir Singh wrote: >if we were to try and resolve this without >removing rpms, what would >that solution look like ? Increment epoch. Almost as tasty as removing rpms.
incrementing epoch will cause a chain of other issues so I don't think it's the good way to go here.
_______________________________________________ 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>
removing the rpm wont fix the problem for people with the installed current. we'd still need to workout someway to make the default upgrade action do the right thing.
can we use obsoletes here ?
On 11/15/2016 10:28 AM, Sandro Bonazzola wrote:
On Tue, Nov 15, 2016 at 5:20 PM, Lamar Owen lowen@pari.edu wrote:
Karanbir Singh wrote:
if we were to try and resolve this without >removing rpms, what would that solution look like ?
Increment epoch. Almost as tasty as removing rpms.
incrementing epoch will cause a chain of other issues so I don't think it's the good way to go here.
Oh, I know it would; I said that more than a little bit tongue-in-cheek. I would say that removing the faultily-named rpms is the correct first step. Then we have to use yum's downgrade to get the current version. This, by the way, actually works: +++++++++++++++++++++++ [root@localhost ~]# yum downgrade qemu-*-ev Loaded plugins: fastestmirror, langpacks, nvidia Loading mirror speeds from cached hostfile * base: mirrors.advancedhosters.com * elrepo: reflector.westga.edu * epel: archive.linux.duke.edu * extras: mirrors.advancedhosters.com * nux-dextop: mirror.li.nux.ro * trinity-r14: kuiper.mirrorservice.org * trinity-r14-noarch: kuiper.mirrorservice.org * updates: repo1.ash.innoscale.net Resolving Dependencies --> Running transaction check ---> Package qemu-img-ev.x86_64 10:2.3.0-31.el7_2.21.1 will be a downgrade ---> Package qemu-img-ev.x86_64 10:2.3.0-31.el7.16.1 will be erased ---> Package qemu-kvm-common-ev.x86_64 10:2.3.0-31.el7_2.21.1 will be a downgrade ---> Package qemu-kvm-common-ev.x86_64 10:2.3.0-31.el7.16.1 will be erased ---> Package qemu-kvm-ev.x86_64 10:2.3.0-31.el7_2.21.1 will be a downgrade ---> Package qemu-kvm-ev.x86_64 10:2.3.0-31.el7.16.1 will be erased ---> Package qemu-kvm-tools-ev.x86_64 10:2.3.0-31.el7_2.21.1 will be a downgrade ---> Package qemu-kvm-tools-ev.x86_64 10:2.3.0-31.el7.16.1 will be erased --> Finished Dependency Resolution
Dependencies Resolved
================================================================================ Package Arch Version Repository Size ================================================================================ Downgrading: qemu-img-ev x86_64 10:2.3.0-31.el7_2.21.1 centos-qemu-ev 792 k qemu-kvm-common-ev x86_64 10:2.3.0-31.el7_2.21.1 centos-qemu-ev 449 k qemu-kvm-ev x86_64 10:2.3.0-31.el7_2.21.1 centos-qemu-ev 2.1 M qemu-kvm-tools-ev x86_64 10:2.3.0-31.el7_2.21.1 centos-qemu-ev 251 k
Transaction Summary ================================================================================ Downgrade 4 Packages
Total download size: 3.6 M Is this ok [y/d/N]: y Downloading packages: (1/4): qemu-kvm-common-ev-2.3.0-31.el7_2.21.1.x86_64.rpm | 449 kB 00:00 (2/4): qemu-img-ev-2.3.0-31.el7_2.21.1.x86_64.rpm | 792 kB 00:00 (3/4): qemu-kvm-tools-ev-2.3.0-31.el7_2.21.1.x86_64.rpm | 251 kB 00:00 (4/4): qemu-kvm-ev-2.3.0-31.el7_2.21.1.x86_64.rpm | 2.1 MB 00:00 -------------------------------------------------------------------------------- Total 3.2 MB/s | 3.6 MB 00:01 Running transaction check Running transaction test Transaction test succeeded Running transaction Installing : 10:qemu-img-ev-2.3.0-31.el7_2.21.1.x86_64 1/8 Installing : 10:qemu-kvm-common-ev-2.3.0-31.el7_2.21.1.x86_64 2/8 Installing : 10:qemu-kvm-ev-2.3.0-31.el7_2.21.1.x86_64 3/8 Installing : 10:qemu-kvm-tools-ev-2.3.0-31.el7_2.21.1.x86_64 4/8 Cleanup : 10:qemu-kvm-tools-ev-2.3.0-31.el7.16.1.x86_64 5/8 Cleanup : 10:qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64 6/8 Cleanup : 10:qemu-img-ev-2.3.0-31.el7.16.1.x86_64 7/8 Cleanup : 10:qemu-kvm-common-ev-2.3.0-31.el7.16.1.x86_64 8/8 Verifying : 10:qemu-kvm-common-ev-2.3.0-31.el7_2.21.1.x86_64 1/8 Verifying : 10:qemu-kvm-tools-ev-2.3.0-31.el7_2.21.1.x86_64 2/8 Verifying : 10:qemu-kvm-ev-2.3.0-31.el7_2.21.1.x86_64 3/8 Verifying : 10:qemu-img-ev-2.3.0-31.el7_2.21.1.x86_64 4/8 Verifying : 10:qemu-kvm-common-ev-2.3.0-31.el7.16.1.x86_64 5/8 Verifying : 10:qemu-kvm-ev-2.3.0-31.el7.16.1.x86_64 6/8 Verifying : 10:qemu-img-ev-2.3.0-31.el7.16.1.x86_64 7/8 Verifying : 10:qemu-kvm-tools-ev-2.3.0-31.el7.16.1.x86_64 8/8
Removed: qemu-img-ev.x86_64 10:2.3.0-31.el7.16.1 qemu-kvm-common-ev.x86_64 10:2.3.0-31.el7.16.1 qemu-kvm-ev.x86_64 10:2.3.0-31.el7.16.1 qemu-kvm-tools-ev.x86_64 10:2.3.0-31.el7.16.1
Installed: qemu-img-ev.x86_64 10:2.3.0-31.el7_2.21.1 qemu-kvm-common-ev.x86_64 10:2.3.0-31.el7_2.21.1 qemu-kvm-ev.x86_64 10:2.3.0-31.el7_2.21.1 qemu-kvm-tools-ev.x86_64 10:2.3.0-31.el7_2.21.1
Complete! [root@localhost ~]# +++++++++++++++++++++++++++++++
Now you need to remove the faulty RPMs so that yum upgrade won't go back the other direction.