Re: update gives me broken /etc/yum.repos.d/atrpms.repo file

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, Jul 25, 2005 at 03:17:28PM -0400, Phil Schaffner wrote:
> On Mon, 2005-07-25 at 12:58 -0400, Robert P. J. Day wrote:
> > On Mon, 25 Jul 2005, David Cary Hart wrote:
> > 
> > > On Mon, 2005-07-25 at 17:39 +0100, Paul Howarth wrote:
> > > > Robert P. J. Day wrote:
> > > > >   ok, another "yum update" issue.  after a recent update, i got
> > > > > a whack of new /etc/yum.repos.d/*.repo files as part of the
> > > > > medley-package-config package, which included a new (and
> > > > > apparently broken) atrpms.repo file.
> > > >
> > > > Sounds like ATrpms is self-destructing ;-)
> > >
> > > Anecdotally, it looks like 30% of the problems on this list are
> > > related to mixed repos. Axel (who contributes much to the community)
> > > makes matters more complicated with proprietary dependencies.
> > 
> > the issue i ran into was much simpler than that -- the new atrpms.repo
> > file that was installed by the update simply had a bad URL for axel's
> > stable FC4 repo.
> 
> My Axel/ATrpms solution was to disable ATrpms repos in yum after
> experiencing repeated problems with config files being clobbered (when
> creating .rpmnew files would have avoided breakage and problems),

All config files are declared %config(noreplace), i.e. they should do
exactly what you describe. If not, then it's either a bug in the
specfile (forgetting to mark a config file as such, not the case as
far as I can see), or in rpm itself.

> deps of "stable" packages on packages in the "testing" or "bleeding"
> repos, and in general, incompatibility with other repos.

Where are the matching bug reports at bugzilla.atrpms.net? :)

> I use yum for regular updates, but have ATrpms (and a few others)
> configured in smart at a low priority so I can browse the available
> packages with smart-gui and choose any I may want.  More trouble,
> but much less breakage.

Well, some years back I was also a fan of preferences/priorities/
weights whatever. Today I know that they create far more subtle bugs
that can't be debugged in a sane way - like packages sets only being
partly upgraded, and implicit dependencies on other packages (like
modified core ones) being broken.

That's why ATrpms does not ship any predefined preferences/priorities/
weights for repos and lets this be done by the user.
-- 
Axel.Thimm at ATrpms.net

Attachment: pgpIWqMHMpCaW.pgp
Description: PGP signature


[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux