<div dir="ltr">On Wed, Dec 15, 2010 at 9:34 PM, Andrew Flegg <span dir="ltr"><<a href="mailto:andrew@bleb.org">andrew@bleb.org</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div class="im">On Wed, Dec 15, 2010 at 19:30, Mohammad Abu-Garbeyyeh<br>
<<a href="mailto:mohammad7410@gmail.com">mohammad7410@gmail.com</a>> wrote:<br>
><br>
> If any dirty workarounds have to be done, I would've removed Nokia's<br>
> repositories from the trusted list in HAM's configuration file and<br>
> announced the SSU long ago.<br>
<br>
</div>Well, that's still an approach open to us if it's all or nothing.<br>
<div class="im"><br>
> Sadly, no one's offering to help with it, might as well start reading<br>
> all of HAM's source to see what goes where and why.<br>
<br>
</div>Could you bring the list (or, perhaps, maemo-developers) up to speed on:<br>
<br>
a) Where you're at.<br>
b) What the problems are.<br>
c) What approaches you've tried/discounted.<br></blockquote><div><br>I'm sure I sent an email about that last month ;)<br>Anyway, the SSU is all set up and can in fact be used on devices, however,<br>it will only work with apt, and HAM will ignore packages from the repo.<br>
Niels also set up a builder, so we can distribute packages with their sources.<br><br>The postinst file currently adds the GPG key with apt-key, so that's apt-get<br>working fine with packages being authorised and all.<br>
<br>It also adds the fingerprint of the key to HAM's config file, and with the latest<br>package, it also adds <certified/> to the config, as is done with the official<br>SSU repos, the trust level is also set to 650, higher than all other repos,<br>
yet HAM still ignores the packages.<br><br>Another problem at hand is that we're replacing Nokia's meta packages with<br>our own ones (locales aren't depended on, so one package should work on<br>all firmwares (002, 003 etc...)), however, to do this, apt and HAM should not<br>
be running, and a terminal window has to be launched from the postinst<br>(which, for some reason, works when installing with dpkg, but not with apt).<br><br>The last problem isn't something to worry about, I guess we can make a quick<br>
GUI to enable and/or disable the community SSU, which the user clicks after<br>installation, it's a one-time process for the user.<br><br>So the only major problem right now is HAM ignoring packages from the repository,<br>
or the "wrong domain" as logs show.<br> <br>Regards,<br>Mohammad Abu-Garbeyyeh<br></div></div><br></div>