[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media

Maarten Vanraes maarten.vanraes at gmail.com
Thu Jun 21 13:30:10 CEST 2012

> 21.06.2012 13:35, AL13N kirjutas:
>> B. fetch dependencies only from enabled repositories
>> Problems:
>>  - if backports are enabled, dependencies could come from backports
>> instead of release.
>> Solutions for this:
>>  - this can be prevented in various ways: even as simple as the backport
>> packager to bump an update with stricter requires so that the backport
>> wouldn't be fetched (_IF_ it indeed would be incompatible) AND the
>> update
>> could have stricter requires for that new dependency.
> I still can't see how are you going to solve this case:
> I have backports enabled. There are packages that are newer than the one
> in release. I
> haven't installed them. Now new update requires such package that is both
> in release and in
> backports. Update will pull package from enabled backports as they are
> newer - i didn't want
> that. And you can't just submit new backport that blocks it. Older
> backports are still
> there. So you can install those if new backport doesn't work for you (the
> same we have for
> updates at the moment).

IF the update cannot work with the backported new dependency, it should be
strict required in the update. in that case, the one from release will be

if the update does work with the backport, then i don't see why you
wouldn't want that, since you enabled backports.
==> this sounds like cherry-picking backports.

in other words, you're advanced enough to find out what you want, because
i don't think we can support all forms of cherry-picking backports.

More information about the Mageia-dev mailing list