[Mageia-sysadm] Copying packages from release to updates_testing
stormi at laposte.net
Mon Oct 10 16:00:01 CEST 2011
Le dimanche 9 octobre 2011 04:59:45, andre999 a écrit :
> David W. Hodgins a écrit :
> > On Tue, 06 Sep 2011 14:05:02 -0400, Michael Scherer <misc at zarb.org>
> > wrote:
> >> Packagers should list them, we will manage to copy when needed.
> > Going to be getting a new type of copy request shortly.
> > As demonstrated by https://bugs.mageia.org/show_bug.cgi?id=2977
> > where updating mencoder from the Core Release version to the
> > Tainted Release version is failing, as the libtwolame package
> > is not available to the Tainted Release repository.
> > Arrgh. Please ignore the message for now. I'm still trying
> > to figure out exactly what is going on with this one.
> What we need is the build system to do something like :
> Updates to tainted to search for requires in
> 1) first tainted/updates
> 2) then tainted/release
> 3) then core/updates and release, nonfree/updates and release
> Similarly, for updates to nonfree it would be
> 1) first nonfree/updates
> 2) then nonfree/release
> 3) then core/updates and release
> And updates to core
> 1) first core/updates
> 2) then core/release
> So in other words, we need a table to tell the build system where to look.
> With at least a 2-stage search, for efficiency.
> (which is apparently already more or less planned.)
> The above doesn't take into account i586/x86_64, or backports.
It's not related to the build system, and urpmi already does that (not exactly
following your algorithm, but the dependency solving is working). The problem
is only in MageiaUpdate.
More information about the Mageia-sysadm