Bug 1033555 - yum-plugin-fs-snapshot uses an obsolete module that can't be installed
Summary: yum-plugin-fs-snapshot uses an obsolete module that can't be installed
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: yum-utils
Version: 19
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Packaging Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-22 11:29 UTC by Vadim Troshchinskiy
Modified: 2015-02-18 11:00 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-18 11:00:18 UTC
Type: Bug


Attachments (Terms of Use)

Description Vadim Troshchinskiy 2013-11-22 11:29:36 UTC
Description of problem:

Tried to install the plugin. On first run, got this: "Snapshot support not available, no python-lvm package installed".

Ok, so "sudo yum install python-lvm". This says:
Package python-lvm is obsoleted by lvm2-python-libs, trying to install lvm2-python-libs-2.02.98-13.fc19.x86_64 instead

After installing it, I get "Snapshot support not available, no python-lvm package installed" again. I suppose it really wants the obsoleted package.


How reproducible:

Happens every time

Steps to Reproduce:
1. Install yum-plugin-fs-snapshot
2. yum install python

Actual results:

Still doesn't work

Expected results:

Plugin should work

Comment 1 Zdeněk Pavlas 2013-11-22 12:01:53 UTC
What version of yum-plugin-fs-snapshot are you using?
yum-plugin-fs-snapshot-1.1.31-18.fc19.noarch.rpm does not use python-lvm, neither is there such error message.

Comment 2 Vadim Troshchinskiy 2013-11-22 14:17:44 UTC
The same you said.

[qindel@snark ~]$ rpm -qa | grep yum-plugin-fs-snapshot
yum-plugin-fs-snapshot-1.1.31-18.fc19.noarch
[qindel@snark ~]$ sudo yum fssnapshot
Loaded plugins: auto-update-debuginfo, changelog, fs-snapshot, langpacks, refresh-packagekit, verify
Snapshot support not available, no python-lvm package installed.
fssnapshot summary done
[qindel@snark ~]$ sudo yum install python-lvm
Loaded plugins: auto-update-debuginfo, changelog, fs-snapshot, langpacks, refresh-packagekit, verify
Package python-lvm-1.9.2-2.fc19.x86_64 is obsoleted by lvm2-python-libs-2.02.98-13.fc19.x86_64 which is already installed
Nothing to do
[qindel@snark ~]$

Comment 3 Zdeněk Pavlas 2013-11-22 14:45:59 UTC
That check must be outside of the plugin, in some other component.. I'll find a f19 machine next week and investigate this.

Comment 4 Fedora End Of Life 2015-01-09 22:22:18 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2015-02-18 11:00:18 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.