[Mageia-dev] bug 2317 revisited: --update option should behave like --search-media
alien at rmail.be
Fri Jun 22 12:20:41 CEST 2012
> 22.06.2012 00:01, AL13N kirjutas:
>> however, as long as backports is installed, it could still be that due
>> to an
>> update a new dependency from release is pulled, which could conflict (or
>> work correctly) with some of the installed backports.
> Like has been said for many times now, you should not backport such
but that's my point, you can't guarantee it, because it's a new dependency
from an update. _any_ package can be the new dependency. even one that was
> And about the conflicting part - well, at that point you are already on
> your own, at least
> as i see it. Backports can break updating/upgrading, we can't avoid that
> (and for the same
> reason backports should be cherry-picked, so you get as little trouble as
> possible). The
> best you can do at that point is to submit a bug about broken update and
> maybe (just maybe)
> we can submit the updated package that needs those new deps into backports
> too - so you can
> pull it from there and get over the update problem. But this should be a
> rare case anyway.
Breaking updates because we try to support backports is not something that
i wish to have, no matter how rare the case.
And your solution wouldn't work, except for backporting the update and
having the user manually try to use the backported version for that too...
>> D. not supporting backports
>> for update validation of package X (let's call it update A2):
>> 1. testing combination: A,C,E for arch i586
>> 2. testing combination: A,C,E for arch x86_64
>> for backport validation of package X (let's call it backport B2):
>> No testing
>> Validations required: 2 for each update
>> => this is how it is now
> And for updates it should stay like that.
both B2, C and D have the same amount of tests for updates.
i thought i had made this clear, but it seems i failed in this.
More information about the Mageia-dev