[Mageia-sysadm] Copying packages from release to updates_testing
Samuel Verschelde
stormi at laposte.net
Mon Oct 10 15:57:45 CEST 2011
Le samedi 8 octobre 2011 23:08:42, 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.
>
> We are going to have to go through all of the packages in the
> Tainted Release repository, and every dependency that those
> packages have, that are not dependencies in the Core Release
> version, will have to be linked to Tainted Release.
>
> Note that these link requests will be requests to link
> from Core Release to Tainted Release, not Tainted Release Updates.
>
> Can links be done to from Core Releaes to Tainted Release?
>
> I know the Release repositories are not supposed to change
> after release. The other option, would be to release a tainted
> update, for any package like mencoder where there are dependencies
> missing in tainted release.
>
I think we must not touch the media regarding this issue which happens only
when a user sets Tainted Release as an update media. While this may be a valid
choice from them, this will be too painful to solve using the "linking"
method, so the real answer is fixing bug #2317 so that MageiaUpdate is able to
pull the needed dependencies.
Samuel
More information about the Mageia-sysadm
mailing list