<br><br><div class="gmail_quote">2010/6/17 Graham Cobb <span dir="ltr"><<a href="mailto:g%2B770@cobb.uk.net">g+770@cobb.uk.net</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Thursday 17 June 2010 09:45:12 Bjoern Ricks wrote:<br>
> hildon-application-manager complains about conflicts with already installed<br>
> packages which should be updated too. Also this behaviour isn't reliable<br>
> and reproducable. On some devices it may work. It is ALWAYS possible to<br>
> install all new packages without any complains with apt-get upgrade.<br>
<br>
<br>
</div>It sounds like you are hitting the HAM protection mechanisms. Basically, HAM<br>
tries to prevent packages being updated from repositories other than the one<br>
which installed it. In fact, it isn't as simple as that, as HAM has a system<br>
of repository priorities based on signing keys. But the bottom line is that,<br>
based on which repositories are involved, HAM will not allow some package<br>
upgrades which apt-get will be perfectly happy to do.<br>
</blockquote></div><br>The packages are from the same repository (<a href="http://files.kolab.org/local/maemo">http://files.kolab.org/local/maemo</a>) but maybe from different sections. Maybe that is also a problem then.<br>
<br>