[packagekit] Res: blocked updates

[Sebastian Heinlein]

Am Freitag, den 15.08.2008, 10:23 -0700 schrieb
dantti85-pk at yahoo.com.br:
> >> but what is a blocked update anyway!? is like a conflicting update?
> 
> >An update you can't install for one reason or another. I don't think
> we
> >should use blocked updates if we can help it, as they're not very
> easy
> >to understand from the user.
> 
> Sorry Richard for asking again about this but
> i couldn't understand very well.
> Should i let the user to select and call installUpdates()
> with a blocked update?
> 
> Or you was just saying that the backend shouldn't emit those?
> In this case we might remove the enum IMHO.
> 
> I found that showing the user and not letting
> them to select it is a safer solution
> although it's not clear why he can't install it.

Especially in the case of security updates it is important for the user
to know about those - even if they can not be installed by using
packagekit.

For Debian and Ubuntu there is a policy to not allow updates which
affect other packages for the stable series.

Furthermore having the DistroUpgrade hook soon the problematic upgrades
should be handled by Ubuntu's dist-upgrader. The dist-upgrader is
cleverer in not breaking your system compared to the default apt
dependency resolver. This behavior is already implemented in Ubuntu's
update-manager.

Cheers,

Sebastian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <http://lists.freedesktop.org/archives/packagekit/attachments/20080816/ea1d0da0/attachment-0004.pgp>