I just updated viewvc on EL-4 from 1.0.9-1.el4 to viewvc-1.1.4-1.el4 and as a result of this, the httpd integration part of viewvc silently disappeared. yum was not able to notify me about it, and there's no mention of it in package changelogs. The Bodhi update notes look fine, but nevertheless this kind of an update is not something I personally expect to see in mid-release EL-*, especially because I believe that (untested) the fix would have been a simple one: I think a simple "Obsoletes: viewvc < 1.1.3" added to the viewvc-httpd package would have fixed it by making yum pull in both viewvc 1.1.x and viewvc-httpd 1.1.x over the existing viewvc 1.0.x - please test and if it works, consider doing that in a soon-to-follow update so fewer people will hit this issue.
Right. Never thought of this. Anyhow, even if we do this, I think the end result may still be broken, because the the config file may be different. I'll put it in and we'll see how it goes.
viewvc-1.1.5-2.el4 has been submitted as an update for Fedora EPEL 4. http://admin.fedoraproject.org/updates/viewvc-1.1.5-2.el4
viewvc-1.1.5-2.el4 has been pushed to the Fedora EPEL 4 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update viewvc'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/viewvc-1.1.5-2.el4
Any feedback on this new package?
Only that it seems to upgrade cleanly from 1.1.4-1.el4; I already solved the problems created by the 1.1.4-1.el4 upgrade manually and don't have a box to play with recreating the problem. Did you test it yourself? I suppose it'd be fairly easy if you have a box that can be used for testing: install the last 1.0.x package, modify its config files, see what happens when upgrading with yum from that to this version. viewvc-httpd should be pulled in.
I'm flying blind on this one - I have no RHEL4/CentOS4 machines at all.
OUCH! Have you sought for co-maintainers? If nobody is available, I suggest orphaning the package for EL versions you can't test with. If you ask me, for an EL distro it's better to not have a package for something at all than to get shipped something that the maintainer isn't able to test...
(In reply to comment #7) > OUCH! Have you sought for co-maintainers? No, not really. > If nobody is available, I suggest > orphaning the package for EL versions you can't test with. If you ask me, for > an EL distro it's better to not have a package for something at all than to get > shipped something that the maintainer isn't able to test... So far it worked by using testing repository. I'd put the package in (which I use on Fedora, so I know it'll be mostly OK). Testers give me feedback on broken stuff etc. Lemme see if I can set up an EL-4 system somewhere or get access to one.
I think I'm going to push this to stable. All EL-4/5 machines I have access to I cannot fiddle with using yum. Let me know if you're OK with me pushing 1.1.5-2 to stable.
Just from reading the CVS diffs (not actually tested the direct 1.0.x upgrade to it) it seems okay to me.
viewvc-1.1.5-2.el4 has been pushed to the Fedora EPEL 4 stable repository. If problems still persist, please make note of it in this bug report.