2:07 p.m.
Hi,
I just upgraded my engine from 4.1.9 to 4.2.8 to 4.3.x yesterday. One
issue I hit along the way was a complaint about repos being listed more
than once:
Repository virtio-win-stable is listed more than once in the configuration
Repository centos-sclo-rh-release is listed more than once in the configuration
I also received errors like:
http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.8/repodata/rep...: [Errno
14] HTTP Error 404 - Not Found
Trying other mirror.
Even after I did a yum erase on ovirt-release40 (and ovirt-release41) I
noticed that the 4.0 and 4.1 yum repositories (and dependencies)
configurations were left in /etc/yum.repos.d/. Is there a reason these
files are not removed when the associated release packages are removed?
Thanks,
-derek
--
Derek Atkins 617-623-3745
derek(a)ihtfp.com www.ihtfp.com
Computer and Internet Security Consultant
8:18 a.m.
New subject: What to do with old ovirt yum repos, and why are they kept around?
On Mon, Oct 28, 2019 at 3:09 PM Derek Atkins <derek(a)ihtfp.com> wrote:
Hi,
I just upgraded my engine from 4.1.9 to 4.2.8 to 4.3.x yesterday. One
issue I hit along the way was a complaint about repos being listed more
than once:
Repository virtio-win-stable is listed more than once in the configuration
Repository centos-sclo-rh-release is listed more than once in the configuration
I also received errors like:
http://mirror.centos.org/centos/7/storage/x86_64/gluster-3.8/repodata/rep...: [Errno
14] HTTP Error 404 - Not Found
Trying other mirror.
Even after I did a yum erase on ovirt-release40 (and ovirt-release41) I
noticed that the 4.0 and 4.1 yum repositories (and dependencies)
configurations were left in /etc/yum.repos.d/. Is there a reason these
files are not removed when the associated release packages are removed?
There is a reason. I am not sure this reason is the only way, so there might be
a solution. If you want, feel free to open a bug about it. Patches are
welcome :-)
The reason is that the repo files are owned by the package, but are not included
in it. We have a single release package for all distros. During %post,
code runs,
checks which distro you use, and copies the relevant files. I guess a simple fix
is to remove them in %postun, but I guess this is a bit tricky (need
to handle well
upgrades, need to consider whether you (the user) changed the files and so
if we should somehow check this and then not remove, etc.), which is why it
never happened (and also because no-one complained, although personally I
also was annoyed a bit by this, but always simply removed the files manually).
Best regards,
--
Didi
1645
days inactive
1646
days old
1 comments
2 participants
participants (2)
-
Derek Atkins -
Yedidyah Bar David