[mythtv-users] Re: ATRPM Issues Upgrading .14 > .15

[MythTV]

Axel:

Thanks for the quick response and for all your hard work on the RPMs!  I
followed your directions and -- with the addition that I had to go get
wget 1.9.1 from your site (which I had read about earlier) -- it all
worked like a charm.

Thanks again, and hopefully one day I can return the favor.

George

On Sat, 2004-05-29 at 16:00, Axel Thimm wrote:
> On Sat, May 29, 2004 at 01:29:51PM -0400, MythTV wrote:
> > I just tried upgrading from 0.14 to 0.15 using Axel's RPMs, but when I
> > tried apt-get dist-upgrade prior to installing the new version of Myth I
> > got the following:
> > 
> > Failed to fetch
> > http://dag.atrpms.net/redhat/fc1/en/i386/base/pkglist.dag  301 Moved
> > Permanently
> > Failed to fetch
> > http://spc.atrpms.net/fedora/linux/1/i386/base/pkglist.spc  404 Not
> > Found
> 
> You are not really a frequent updater, are you? ;)
> 
> Try running
> 
> rpm -Uhv http://download.atrpms.net/production/packages/fedora-1-i386/atrpms/atrpms-package-config-66-1.rhfc1.at.noarch.rpm
> 
> first, and fix the sources.
> 
> > [root at localhost mythtv]# apt-get dist-upgrade
> > Reading Package Lists... Done
> > Building Dependency Tree... Done
> > You might want to run `apt-get -f install' to correct these.
> > The following packages have unmet dependencies:
> >   XFree86: Depends: utempter but it is not installed
> >   curl-devel: Depends: openssl-devel but it is not installed
> >   gnome-libs: PreDepends: utempter but it is not installed
> >   libgnome: PreDepends: utempter but it is not installed
> >   mythweb: Depends: php-mysql (>= 4.2.2) but it is not installed
> >   redhat-config-packages: Depends: libxml2-python but it is not
> > installed
> >   rhn-applet: Depends: up2date-gnome (>= 4.1.5) but it is not installed
> >   screen: Depends: libutempter.so.0
> >   xterm: Depends: libutempter.so.0
> >   yum: Depends: libxml2-python but it is not installed
> > E: Unmet dependencies. Try using -f.
> 
> This means your system has been ripped out some rpm with --nodeps, or
> your rpm database is out of order. I'd rebuild the database, and if it
> is still giving these errors, I'd let apt-get -f install try to fix the system.