On Mon, Aug 09, 2004 at 09:22:46AM -0600, Robin Laing wrote:
I was running into problems with yum and up2date on two computers and have traced all problems to atrpms repository. For some reasons their files don't want to work with other repositories as nice as others. I ran into this problem with many little programs on the weekend that I had to remove close to 100 atrpm packages and re-install from other repositories to clean my system. Many won't even work nicely with the normal fedora updates. I still have alot of sorting out to do.
My biggest problem has been with their PHP* packages and I have submitted a bug report which has been closed but still won't work as expected.
You mean
http://bugzilla.atrpms.net/show_bug.cgi?id=143
What does not work as expected? If you don't report it it won't get fixed.
Note: the php packages are almost genouine Fedora, in fact they are build from effectively the same src.rpm, only against newer libxslt.
I cannot connect to the bugzilla site at this time but my files indicate that this is the php problem that I submitted. The latest PHP updates from fedora-updates won't install due to the libxsltbreakpoint dependency which is the bug that I issued.
The problem with atrpms goes deeper. I came back from three weeks holidays and tried to do all the updates and install a few packages. Newer packages, including those from fedora-updates were being stopped due to dependency problems for many packages, I don't have the list anymore. Needless to say that it took many hours to update what should have taken minutes with yum. I had to remove packages which all but one turned out to be from atrpms. Multimedia/dvd applications are some of the problems. Same problems on two different computers. I could have used the same notes. It took over an hour yesterday to update just one set of libs as I had to remove other applications that were dependent on other libs that were used by other applications. Nice circle.
There has been discussions about different repositories and how they work together. I have had faith that repositories should work well together and this I believe is the feeling from all users and developers. If I have an application from dag and there is an update from fedora-updates, I should not have to worry about different dependencies and for that matter, it should be dealt with by yum or apt.
As I stated, this is my experience and as I seem only to have to remove atrpms packages to do updates or install programs, it is a problem. When I get a message about a newer lib or application that I go to install or update and it requires me to remove and re-install four, five or more packages from one repository then it is a problem that I don't want to deal with. This is for one application.
As stated in the subject, yum caused a problem and it has in my case. My problems all seem to point to one location with yum and up2date as I had put atrpms in the conf files for both.
When I get time and I can connect to bugzilla I will submit a bug on the whole mess. Simply, it points to how packages work with other repositories. I will have to figure out how to word the issue as it isn't just one package application but a system.
As a suggestion to different repository operators is to run a few machines that do updates from different repositories to check for these various problems and to ensure ease of use for all users. The nodeps option should not be needed.
-- Robin Laing
