Description of problem: The packaging of e2fsprogs is not tracking updated dependency requirements in it's required shared libraries. Let's use libcom_err and the update that occurred between 1.41 and 1.42 as an example. In e2fsprogs commit 4259052093da329907e255b11bf3e799872828c7 set_com_err_gettext() was added to libcom_err. The tools in the 1.42 release of e2fsprogs now require this symbol. However since there is no "Requires: libcom_err >= 1.42" in the FC17 e2fsprogs if one were to simply use rpm -U to upgrade from e2fsprogs-1.41.14-2.fc15.x86_64.rpm (which is in FC16, despite the fc15 tag in it's name) to e2fsprogs-1.42-4.fc17.x86_64.rpm one would get the new e2fsprogs, and e2fsprogs-libs but would not get the newly required libcomm_err and would end up with tools from e2fsck that would fail as they can't find a set_com_err_gettext().
Ok, I'll add the explicit depends to keep all subpackages together. I can't do anything about Gnome3 though ;)
I'll add libss as well. So now e2fsprogs will require: Requires: e2fsprogs-libs = %{version}-%{release} Requires: libcom_err = %{version}-%{release} Requires: libss = %{version}-%{release} which would keep it all in lockstep. Sound right to you?
(In reply to comment #1) > Ok, I'll add the explicit depends to keep all subpackages together. Cool! What's interesting is that this seems to be done already for EL6, looking at some recent spec files for it. > I can't > do anything about Gnome3 though ;) I'm not sure anyone can at this point. :-( I suppose with enough time and effort nothing is impossible though.
(In reply to comment #2) > I'll add libss as well. So now e2fsprogs will require: > > Requires: e2fsprogs-libs = %{version}-%{release} > Requires: libcom_err = %{version}-%{release} > Requires: libss = %{version}-%{release} > > which would keep it all in lockstep. > > Sound right to you? It does, yes. And moreso, it does what EL6 seems to be doing now/already.
Hm, so it does. Shame on me for not changing Fedora at the same time.
e2fsprogs-1.42.3-3.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/e2fsprogs-1.42.3-3.fc17
Package e2fsprogs-1.42.3-3.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing e2fsprogs-1.42.3-3.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-12134/e2fsprogs-1.42.3-3.fc17 then log in and leave karma (feedback).
If you do this, why not use %?_isa, too? https://fedoraproject.org/wiki/Packaging:Guidelines#Requiring_Base_Package
e2fsprogs-1.42.3-3.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.