Hi, On Sat, Oct 01, 2005 at 03:18:11PM +0200, Christoph Wickert wrote: > Am Samstag, den 01.10.2005, 09:15 +0200 schrieb Axel Thimm: > > On Fri, Sep 30, 2005 at 08:08:50PM +0200, Christoph Wickert wrote: > > > Am Freitag, den 30.09.2005, 10:03 -0600 schrieb Robin Laing: > > > > > > > I would try smartpm but there is no FC4 version. > > > > > > http://www.atrpms.net/dist/fc4/smart/ > > > > > > But be careful: I found the medley-package-config package required by > > > this package to be very annoying. I hat working apt and yum config files > > > before and medley-package-config produced a lot of errors that I had to > > > fix by hand. > > > > The medley-package-config is not required for smart, you can use > > atrpms-package-config also. > "extras" is already defined in fedora-extras.repo from fedora-release, > it's defined again in fedoraextras.repo from medley-package-config. With > atrpms-package-config "updates-testing" still has a duplicate entry, since > it is already defined in fedora.repo and again in base.repo from your > package. You didn't fully upgrade to ATrpms' contents, this happens on partial upgrades/installs. Unfortunately FC changes its deployment method of depsolver config files on every release. The mostly sane config was to split the fedora-release into a proper release package and a depsolver config package, where the latter can be extended or simply replaced. But you only get this split, if you do an upgrade against ATrpms. Now, some will see an opportunity to cry out "murderer" and "how can you touch Fedora Core packages" and so on. Whoever cares can find miriads of threads on several lists that discuss these issues, please keep this thread clean ;) > IMHO all your *-package-config rpms should ether be _fully_ compatible > at least to fedora-release They are as a set of packages (and that's how any repo should be considered IMHO), you need to make a full upgrade. > (since it is part of a core install, maybe livna-release, too) or > smart/apt from your repo should not depend on them. They don't, try rpm -qR smart/apt, there is no trace of any *-package-config. This is intended, so anyone can reuse the depsolvers with his own *-package-config (or *-release) package. All the packages require is a repo-agnostic file dependency on their master config file(s). I don't argue that this is the perfect solution, only a good working one for using several repos with several depsolvers. There are probably better ways to do it, and if you find one, I'll gladly accept patches :) > P.S.: Nether medley-package-config nor atrpms-package-config are listed > at www.atrpms.net. Did you try google? It's the first link in http://www.google.com/search?q=site%3Awww.atrpms.net+medley-package-config+atrpms-package-config or try rpm -qi on the package to see that its srpm is 3rd-party-package-config and go to http://atrpms.net/3rd-party-package-config/ -- Axel.Thimm at ATrpms.net
Attachment:
pgpJbaKZsUo0B.pgp
Description: PGP signature
