#8206 Remove libmodulemd from epel7server-infra
Closed: Fixed 4 months ago by kevin. Opened 4 months ago by mprahl.

@sgallagh and I are maintaining a newer version of libmodulemd (currently 2.4) to deploy with MBS in the epel7Server-infra repo. Now that @sgallagh has released libmodulemd2 2.8 in EPEL7, we'd like to stop maintaining libmodulemd in the epel7Server-infra repo and use libmodulemd2. This means that anything that installs libmodulemd and uses the epel7Server-infra repo will start installing libmodulemd 1.6 from RHEL. The benefit of removing libmodulemd from epel7server-infra is that it will allow MBS to install libmodulemd2 for its own use and still be able to install python2-dnf from RHEL which requires libmodulemd. Currently, libmodulemd2 and the libmodulemd in the epel7Server-infra repo conflict.

I believe all I need to do is untag those libmodulemd builds to remove them from the epel7Server-infra repo, but I'd permission from the Fedora Infrastructure team to do so.

So, looking I see the following machines with the 2.4.0 version installed:

batcave01.phx2.fedoraproject.org | CHANGED | rc=0 | (stdout) libmodulemd-2.4.0-1.el7.infra.x86_64
batcave13.rdu2.fedoraproject.org | CHANGED | rc=0 | (stdout) libmodulemd-2.4.0-1.el7.infra.x86_64
mbs-backend01.phx2.fedoraproject.org | CHANGED | rc=0 | (stdout) libmodulemd-2.4.0-1.el7.infra.x86_64
mbs-frontend01.phx2.fedoraproject.org | CHANGED | rc=0 | (stdout) libmodulemd-2.4.0-1.el7.infra.x86_64
mbs-frontend02.phx2.fedoraproject.org | CHANGED | rc=0 | (stdout) libmodulemd-2.4.0-1.el7.infra.x86_64

I think batcave01 was back from when smooge was trying to run gobbitsplitter on it, so it shouldn't matter.

So, yes, it seems like it should be fine/safe to untag all the libmodulemd's from epel7-infra/stg

I have done so now, but I also see in epel7-infra-stg:

libmodulemd1-1.8.11-1.el7.infra           epel7-infra-stg       sgallagh
libmodulemd1-1.8.11-2.el7.infra           epel7-infra-stg       sgallagh
libmodulemd1-1.8.13-1.el7.infra           epel7-infra-stg       kevin

Should those be untagged also, or left? @sgallagh ?

Metadata Update from @kevin:
- Issue priority set to: Waiting on Reporter (was: Needs Review)

4 months ago

@kevin Yes, that should also be killed off. If anything breaks as a result, we need to fix it to use the official copy from RHEL.

ok. Done.


Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 months ago

@kevin, I'm sorry but could you please also untag libmodulemd1-1.8.10-1.el7.infra since it obsoletes libmodulemd-1.6.3-1.el7.x86_64 which is the one shipped in RHEL?

Metadata Update from @mprahl:
- Issue status updated to: Open (was: Closed)

4 months ago

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 months ago

Login to comment on this ticket.