Re: Community updates for diablo
On Tue, May 04, 2010 at 06:50:21PM +0100, Graham Cobb wrote: Will there be any SDK/autobuilder updates to go with this? Not required right now, but it's an interesting question. For example, one existing request is to enable ogg support in sdl-mixer which would require /something/ to be done in order for extras apps to be able to use it. I'm not sure what the right solution would be. The recent work on the Fremantle side seems particularly relevant, but may be too much work for this. Niels, what do you think? I am assuming anything built with the current autobuilder should work with this community update -- is that right? Are there any updates to any libraries? Everything should work fine for now. There are some libraries in the updates but they only contain bug fixes (no API changes). L. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo
Hi, Just reminder about official Diablo kernel fix for USB networking with Windows PCs that seems to be missing from the list. Patch and rebuilt Diablo kernel can be downloaded from here: http://tablets-dev.nokia.com/maemo-dev-env-downloads.php. See file diablo_kernel_usbnet_patch_windows_v0.4.zip for details. kernel-diablo: * Fixes: BMO#2249: FM Radio frequency not set for use in Japan. Martin Grimme martin.grimme at lintegra.de * Fixes: BMO#2491: cant run camera applications with v4l2. Sakari Ailus sakari.ailus at nokia.com * Fixes: BMO#3123: Patch to kernel to allow DSP framebuffer sharing on N8x0 devices. Simon Pickering S.G.Pickering at bath.ac.uk * Fixes: BMO#3519: Integrate screen rotation patches into stock kernel. Luarvique L. Luarvique luarvique at gmail.com * Changed debian/rules to do a parallel make because Diablo's dpkg-buildpackage is too old to support -j and I'm lazy. This patch we did is actually back port from generic Linux kernel to Diablo as this was generic problem in Linux kernel at Diablo times. Cheers, //Jarmo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo
On Tue, May 04, 2010 at 06:50:21PM +0100, Graham Cobb wrote: Will there be any SDK/autobuilder updates to go with this? Not required right now, but it's an interesting question. For example, one existing request is to enable ogg support in sdl-mixer which would require /something/ to be done in order for extras apps to be able to use it. I'm not sure what the right solution would be. The recent work on the Fremantle side seems particularly relevant, but may be too much work for this. Niels, what do you think? The devkit + symbols might be a solution. But that also means that we basically need to create our own SDK :) We can say that the for instance say that from a certain point in time diablo is only supported for devices running the community version of diablo. (Discussion welcome) We would need to create a community sdk repo with the updated libraries too. And the autobuilder would use that sdk. Having both a plain diablo Extras and a community ssu compatible Extras would probably not be worth it as the number of downloads for diablo are really low. Diablo seems to be EOL for Nokia, although not officially announced. Everybody wanting new latest and greatest software should use the community SSU at some point? Extras is a community run repository, whatever the community agrees on goes. I am assuming anything built with the current autobuilder should work with this community update -- is that right? Are there any updates to any libraries? Everything should work fine for now. There are some libraries in the updates but they only contain bug fixes (no API changes). L. -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo
jarmo.ti...@nokia.com wrote: Hi, Just reminder about official Diablo kernel fix for USB networking with Windows PCs that seems to be missing from the list. Many things are missing from the list. I guess the posted list is not final? To me it looks more like what is included in current first testing version. Much longer list of possible fixes seems to be here http://wiki.maemo.org/Talk:Diablo_Community_Project , usb networing fix is listed as g_ether / RNDIS is broken in kernel 2.6.21 ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Community updates for diablo
Hi, -Original Message- From: ext Frantisek Dufka [mailto:duf...@seznam.cz] Sent: 05 May, 2010 16:07 To: Tikka Jarmo (Nokia-D/Helsinki) Cc: maemo-developers@maemo.org Subject: Re: Community updates for diablo jarmo.ti...@nokia.com wrote: Hi, Just reminder about official Diablo kernel fix for USB networking with Windows PCs that seems to be missing from the list. Many things are missing from the list. I guess the posted list is not final? To me it looks more like what is included in current first testing version. Much longer list of possible fixes seems to be here http://wiki.maemo.org/Talk:Diablo_Community_Project , usb networing fix is listed as g_ether / RNDIS is broken in kernel 2.6.21 This list at wiki looks more useful and as you said that USB fix seems to be included. Cheers, //Jarmo ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo
On Mon, May 03, 2010 at 02:14:00PM +0200, Carsten Munk wrote: X-Fade said we should set up a IRC meeting to get this accomplished - he can take care of server side. Cool :-) Got a suggestion for a time during this week? Any evening (UTC) is fine. If it has to be during office hours, Thursday or Friday morning will probably do. I prefer UTC office hours as MeeGo already tends to steal some evenings. L. -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo
Thanks to Niels who spent this afternoon working on this, we now have maemo.org signed repositories! Without further ado, they are: deb http://repository.maemo.org/community/ diablo free non-free deb http://repository.maemo.org/community-testing/ diablo free non-free The community/ one is supposed to be the stable one and is currently empty, while community-testing now holds the contents of my private testing repository. To anyone interested in testing: 1. Understand that these packages are unofficial software updates provided by the maemo.org community with no warranty expressed or implied and are not supported by Nokia. Is is highly recommended that you have a recent backup before proceeding. 2. Make sure you have not (perhaps unintentionally) removed the appropriate osso-software-version-rxXX package for your device, of if you have re-install it as SSU simply won't work without it. 3. Visit http://repository.maemo.org/community-testing/community-testing.install with the built-in browser (microb) and open it with the application manager when prompted. This will install the community-testing repository and an enabler package that loads its public key and sets up the package domain with a higher priority than the nokia-system one so that nokia-system packages can be updated. 4. Refresh the application manager (bottom right button) so it will see the packages in the community-updates domain and offer the update. 5. Install the update. 6. Report any issues to http://talk.maemo.org/showthread.php?t=30648 (for now, I'll be bugging Andre for a bugs.maemo.org product soon). To anyone interested in contributing: look at http://wiki.maemo.org/Talk:Diablo_Community_Project for the backlog and see if anything grabs your interest. N810W (RX48) owners are particularly welcome, as are people who are willing to review source packages :-) L. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Community updates for diablo
I don't know if I missed some previous post but I have some questions: 1. Was diablo officially discontinued by nokia? 2. Where can we find what has changed/benefits of upgrading? 3. Does this in any way or shape relate to having qt 4.6 on Diablo? Does it make any easier/harder? Felipe -Original Message- From: maemo-developers-boun...@maemo.org [mailto:maemo-developers-boun...@maemo.org] On Behalf Of Lucas Maneos Sent: Tuesday, May 04, 2010 12:04 PM To: maemo-developers@maemo.org Subject: Re: Community updates for diablo Thanks to Niels who spent this afternoon working on this, we now have maemo.org signed repositories! Without further ado, they are: deb http://repository.maemo.org/community/ diablo free non-free deb http://repository.maemo.org/community-testing/ diablo free non-free The community/ one is supposed to be the stable one and is currently empty, while community-testing now holds the contents of my private testing repository. To anyone interested in testing: 1. Understand that these packages are unofficial software updates provided by the maemo.org community with no warranty expressed or implied and are not supported by Nokia. Is is highly recommended that you have a recent backup before proceeding. 2. Make sure you have not (perhaps unintentionally) removed the appropriate osso-software-version-rxXX package for your device, of if you have re-install it as SSU simply won't work without it. 3. Visit http://repository.maemo.org/community-testing/community-testing.install with the built-in browser (microb) and open it with the application manager when prompted. This will install the community-testing repository and an enabler package that loads its public key and sets up the package domain with a higher priority than the nokia-system one so that nokia-system packages can be updated. 4. Refresh the application manager (bottom right button) so it will see the packages in the community-updates domain and offer the update. 5. Install the update. 6. Report any issues to http://talk.maemo.org/showthread.php?t=30648 (for now, I'll be bugging Andre for a bugs.maemo.org product soon). To anyone interested in contributing: look at http://wiki.maemo.org/Talk:Diablo_Community_Project for the backlog and see if anything grabs your interest. N810W (RX48) owners are particularly welcome, as are people who are willing to review source packages :-) L. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Community updates for diablo
Am Dienstag, den 04.05.2010, 12:16 -0400 schrieb Felipe Crochik: 1. Was diablo officially discontinued by nokia? I don't know of any official statement, however reality shows that it's defacto discontinued (or did you see any Diablo updates in the last 16 months after 5.2008.43-7?). andre -- Andre Klapper (maemo.org bugmaster) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo
On Tue, May 04, 2010 at 12:16:20PM -0400, Felipe Crochik wrote: I don't know if I missed some previous post but I have some questions: Most of the discussion has happened in http://talk.maemo.org/showthread.php?t=30648. 1. Was diablo officially discontinued by nokia? Not explicitly as far as I know, but at this stage I think it's safe to assume there will be no more updates unless something extraordinary happens. 2. Where can we find what has changed/benefits of upgrading? Here's the collected changelog of what's currently in the repository (it's also visible in the application manager before upgrading): busybox: * Fixes: BMO#3917: Missing Large File Support (CONFIG_LFS) in Busybox. * Fixes: BMO#3951: Incompatible quote handling in Busybox xargs (FEATURE_XARGS_SUPPORT_QUOTES disabled?) * Enable FEATURE_XARGS_SUPPORT_ZERO_TERM for consistency with FEATURE_FIND_PRINT0 (mentioned in BMO#3951/BMO#4248). * Fixes: BMO#3957: Busybox does not support ls -Q which some scripts need. * Fixes: BMO#3968: grep -r can output corrupt data in error message if file cannot be read. * Fixes: BMO#4174: shell history file is overwritten after every command. * Fixes: BMO#4175: History cross-contamination between concurrently running shells * Fixes: BMO#7014: ash saves only 15 lines of history (increased to 100). * Workaround for BMO#5317: Shell does not save command history / Busybox doesn't handle SIGHUP properly. * Fix for multi-column ls -Q output. * Fixes: BMO#419: Enable IPv6 support in busybox (and PING6). * Fixes: BMO#3989: Busybox ls -s dereferences the file. * Fixes: BMO#4248: Enable features in Busybox to increase its tools GNU/Debian compatibility. * Fixes: BMO#4079: busybox df does not handle root filesystem on command line. * Fixes: BMO#6606: No getopts, called by init-functions (lsb-base). * Fixes: BMO#8291: Enable CONFIG_LOCALE_SUPPORT in busybox. * Build with -mthumb to match the official Nokia package. * Make df rootfs mangling conditional on filesystem arguments. dnsmasq: * Fixes: BMO#995: DNS resolution ignores local domain. * Removed unused resolvconf script. kernel-diablo: * Fixes: BMO#2249: FM Radio frequency not set for use in Japan. Martin Grimme martin.grimme at lintegra.de * Fixes: BMO#2491: cant run camera applications with v4l2. Sakari Ailus sakari.ailus at nokia.com * Fixes: BMO#3123: Patch to kernel to allow DSP framebuffer sharing on N8x0 devices. Simon Pickering S.G.Pickering at bath.ac.uk * Fixes: BMO#3519: Integrate screen rotation patches into stock kernel. Luarvique L. Luarvique luarvique at gmail.com * Changed debian/rules to do a parallel make because Diablo's dpkg-buildpackage is too old to support -j and I'm lazy. loudmouth: * Fixes: BMO#3455: telepathy-gabble deadlooping * Fixes: BMO#4119: digest-uri omits the serv-name part causing authentication failure when host != serv-name Sjoerd Simons sjoerd at debian.org modest: * Fixes: BMO#2553: Please make folder view finger-sized. Daniel Martin Yerga dyerga at gmail.com * Fixes: BMO#2554: Add Move to folder button in main view. Daniel Martin Yerga dyerga at gmail.com * Fixes: BMO#3004: Modest pops up even when only read messages are in IMAP inbox. Daniel Martin Yerga dyerga at gmail.com * Fixes: BMO#3498: Add Zooming to x% messages to Modest. Daniel Martin Yerga dyerga at gmail.com * Fixes: BMO#3941: Signature separator misses trailing space (RFC 3676 violation). tinymail: * Fixes: BMO#4803: Modest sends empty ENABLE command when IMAP server advertises ENABLE but not CONDSTORE or QRESYNC capabilities. osso-pdf-viewer: * Fixes: BMO#2150/NB#76448/NB#120388: PDF Reader doesn't support internal document hyperlinks. xujun Jun.Xu at plenware.com * Fixes: BMO#2704: PDF Reader needs more zoom levels between 50% and 150% Sandu Gherbe pursisimplu2004 at yahoo.com * Fixes: BMO#2714: Page up should go to Bottom of Previous Page (instead of Top). yanghua Hua.Yang at plenware.com * Fixes: BMO#4930: PDF Reader doesn't use optimal screen width in fit width mode. Hauweele Pierre antegallya at gmail.com xserver-xomap: * Fixes: BMO#3519: Integrate screen rotation patches into stock kernel and X server. Luarvique L. Luarvique luarvique at gmail.com * Force building with vfp on ARM to match the official Nokia package, and since it doesn't compile without it anyway. * Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=6502: RandR fails after some time. Marius Gedminas mgedmin at b4net.lt 3. Does this in any way or shape relate to having qt 4.6 on Diablo? Does it make any easier/harder? No, or at least not yet. I honestly don't know what issues there are to be solved for this, but if there's anything we can do I'm all ears. L. ___ maemo-developers mailing list
Re: Community updates for diablo
Am Dienstag, den 04.05.2010, 17:04 +0100 schrieb Lucas Maneos: 4. Refresh the application manager (bottom right button) so it will see the packages in the community-updates domain and offer the update. At least for me the bottom right button was disabled. I had to click Check for updates first which enabled the button and then listed OS2008 Community SSU 5.2010.16-1, 4.4MB. Installing worked perfectly fine. Congrats and big kudos to everybody involved! andre -- Andre Klapper (maemo.org bugmaster) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo
On Tuesday 04 May 2010 17:04:07 Lucas Maneos wrote: Thanks to Niels who spent this afternoon working on this, we now have maemo.org signed repositories! Without further ado, they are: deb http://repository.maemo.org/community/ diablo free non-free deb http://repository.maemo.org/community-testing/ diablo free non-free The community/ one is supposed to be the stable one and is currently empty, while community-testing now holds the contents of my private testing repository. Will there be any SDK/autobuilder updates to go with this? I am assuming anything built with the current autobuilder should work with this community update -- is that right? Are there any updates to any libraries? Graham ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo
On Sun, Apr 25, 2010 at 09:48:03PM +0100, Lucas Maneos wrote: we've been running tests off a private repository for the past 6 weeks or so. It's a relatively small sample (approximately 25 volunteer testers), but no bricked devices so far so I think it's time to move it to a public repository and hopefully get some more people building packages. You can just grab source and/or binary packages from the private repository, but let me know if you've lost the URL or need anything else. Bump. Is there anything I can do to facilitate the process? Thanks, Lucas ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo
2010/5/3 Lucas Maneos ma...@subs.maneos.org: On Sun, Apr 25, 2010 at 09:48:03PM +0100, Lucas Maneos wrote: we've been running tests off a private repository for the past 6 weeks or so. It's a relatively small sample (approximately 25 volunteer testers), but no bricked devices so far so I think it's time to move it to a public repository and hopefully get some more people building packages. You can just grab source and/or binary packages from the private repository, but let me know if you've lost the URL or need anything else. Bump. Is there anything I can do to facilitate the process? X-Fade said we should set up a IRC meeting to get this accomplished - he can take care of server side. Got a suggestion for a time during this week? Regards, Carsten Munk ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo
On Mon, May 03, 2010 at 02:14:00PM +0200, Carsten Munk wrote: X-Fade said we should set up a IRC meeting to get this accomplished - he can take care of server side. Cool :-) Got a suggestion for a time during this week? Any evening (UTC) is fine. If it has to be during office hours, Thursday or Friday morning will probably do. L. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo
On Mon, Mar 01, 2010 at 05:34:52PM +0100, Jeremiah Foster wrote: So what is the next step Lucas? Do we want to put something into the community repo to test if it works - then put in the updates on the Maemo.org servers running reprepro? Hi, we've been running tests off a private repository for the past 6 weeks or so. It's a relatively small sample (approximately 25 volunteer testers), but no bricked devices so far so I think it's time to move it to a public repository and hopefully get some more people building packages. You can just grab source and/or binary packages from the private repository, but let me know if you've lost the URL or need anything else. There are a couple of changes needed in the community-ssu-enabler package, namely to update it with the official repo keys key fingerprints. It's probably a good idea to bump the trust level up a bit so that early testers can roll over to the new repository without hassle. All of the above is in post-install script. BTW, can we have a -testing repo as well? On Mon, Mar 01, 2010 at 09:26:30AM +0200, Marius Vollmer wrote: If anything else comes up, don't hesitate to ask, of course. There is one thing actually: how can I get the application manager to forget a previously set trust-level? I'm doing something along the lines of: # dpkg --purge community-ssu-enabler # apt-get install osso-software-version-rx34=1:5.2008.43-7 (+ all dependencies it complains about) # /usr/bin/flash-and-reboot The prerm script in the first step removes both the domain and key (verified with hildon-application-manager-config dump apt-key list), but the application manager still offers to upgrade after that. It would be nice to have a way of reverting back to the vanilla Diablo state (eg for testing or as a fallback in case things go wrong), so if I've missed something obvious any pointers welcome. Thanks, Lucas ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo (specifically Application Manager if nothing else)
On Mar 1, 2010, at 8:26 AM, Marius Vollmer wrote: ext Lucas Maneos ma...@subs.maneos.org writes: On Mon, Mar 01, 2010 at 08:12:23AM +0200, Marius Vollmer wrote: It might just be the missing public key. Without it, the signature on your repo will not be recognized as valid, and it will be associated with the unsigned domain. After a good night's sleep and some caffeine, I think I found the problem (between the chair and the keyboard). A paste error in the key fingerprint will also have a similar effect (falling back to signed), sorry for the noise. Yep, that's also an important thing to get right, obviously. I am happy that you have figured it out! If anything else comes up, don't hesitate to ask, of course. So what is the next step Lucas? Do we want to put something into the community repo to test if it works - then put in the updates on the Maemo.org servers running reprepro? Jeremiah ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo (specifically Application Manager if nothing else)
(Warning: resurrecting ancient thread, see http://www.gossamer-threads.com/lists/maemo/developers/47855 for background, and http://talk.maemo.org/showthread.php?t=30648 is also relevant). The story so far: - mined a bunch of patches from bugs.maemo.org - built some updated packages with the above - got Nokia's blessing to modify and redistribute osso-software-version-* - set up a test repository. The missing piece: making the updates installable via application manager so we can invite some brave souls for testing. The problem (as I understand it) is packages switching domains. The updated versions come from a repository signed with a different key to the nokia-system one, which makes the application manager ignore them. Based on http://hildon-app-mgr.garage.maemo.org/repos-stable.html: Domains have a 'trust level' associated with them. Domains with a higher trust level are considered to dominate other domains and the AM will allow a package to silently move from a domain to a dominating one. I had assumed that setting a higher trust-level would allow domain switches to happen, but this doesn't seem to be the case :-( For clarity, I'm testing on a freshly-reflashed 5.2008.43-7 N800 with the following added to /etc/hildon-application-manager/domains: domain namecommunity-updates/name trust-level600/trust-level key[...]/key default/ /domain and default/ removed from nokia-system. The application manager log contains just a series of entry pairs like: apt-worker: Ignoring version from wrong domain: modest 1.0-2008.43-2 apt-worker: /var/lib/apt/lists/XXX_Packages So, first things first, am I doing something wrong here? If not, and trust-level alone isn't enough but the updates really need to come from a repository signed with the same key as the originals, are there any other options? Every workaround I can come up with is unworkable at best, the only semi-viable one being to patch the application manager but this has the obvious chicken-and-egg problem of how to publish the patched version so users can install it. I may be missing something obvious, so any ideas welcome. Thanks, Lucas ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo (specifically Application Manager if nothing else)
ext Lucas Maneos ma...@subs.maneos.org writes: The story so far: - mined a bunch of patches from bugs.maemo.org - built some updated packages with the above - got Nokia's blessing to modify and redistribute osso-software-version-* - set up a test repository. Great! The missing piece: making the updates installable via application manager so we can invite some brave souls for testing. The problem (as I understand it) is packages switching domains. The updated versions come from a repository signed with a different key to the nokia-system one, which makes the application manager ignore them. Based on http://hildon-app-mgr.garage.maemo.org/repos-stable.html: Domains have a 'trust level' associated with them. Domains with a higher trust level are considered to dominate other domains and the AM will allow a package to silently move from a domain to a dominating one. I had assumed that setting a higher trust-level would allow domain switches to happen, but this doesn't seem to be the case :-( It should work like you expect it to. For clarity, I'm testing on a freshly-reflashed 5.2008.43-7 N800 with the following added to /etc/hildon-application-manager/domains: domain namecommunity-updates/name trust-level600/trust-level key[...]/key default/ /domain and default/ removed from nokia-system. This looks correct. I suspect that the Application manager just doesn't recognize your repository as belonging to this domain. You also need to install the matching public key. What does # apt-key list output? I can try to find a Diablo device to debug this a bit. It is a bit icky to get all the configurations just right, but once you do, things just start working silently. Every workaround I can come up with is unworkable at best, the only semi-viable one being to patch the application manager but this has the obvious chicken-and-egg problem of how to publish the patched version so users can install it. You can tell people to install it in red-pill mode (or on the command line). In red-pill mode, the domain check can be overruled by the user. I may be missing something obvious, so any ideas welcome. It might just be the missing public key. Without it, the signature on your repo will not be recognized as valid, and it will be associated with the unsigned domain. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo (specifically Application Manager if nothing else)
On Mon, Mar 01, 2010 at 08:12:23AM +0200, Marius Vollmer wrote: It might just be the missing public key. Without it, the signature on your repo will not be recognized as valid, and it will be associated with the unsigned domain. After a good night's sleep and some caffeine, I think I found the problem (between the chair and the keyboard). A paste error in the key fingerprint will also have a similar effect (falling back to signed), sorry for the noise. (Of course I can't test it at the moment because the catalogue.tableteer.nokia.com repositories are timing out. Oh well...) Thanks! Lucas ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo (specifically Application Manager if nothing else)
ext Lucas Maneos ma...@subs.maneos.org writes: On Mon, Mar 01, 2010 at 08:12:23AM +0200, Marius Vollmer wrote: It might just be the missing public key. Without it, the signature on your repo will not be recognized as valid, and it will be associated with the unsigned domain. After a good night's sleep and some caffeine, I think I found the problem (between the chair and the keyboard). A paste error in the key fingerprint will also have a similar effect (falling back to signed), sorry for the noise. Yep, that's also an important thing to get right, obviously. I am happy that you have figured it out! If anything else comes up, don't hesitate to ask, of course. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo (specifically Application Manager if nothing else)
On Tue, Apr 14, 2009 at 17:01, Marius Vollmer marius.voll...@nokia.com wrote: Package domains are 'orthogonal' to catalogues and repositories. They are connected by the signature of the Release file. The AM looks at the keys that have been used to sign the Release file and associates each package with a package domain. Package domains are configured in /etc/hildon-application-manager/domains. You will find the trust level in there, among other things. So the key is the key. All of the entries on my N810 have *two* key elements per entry, and there's already one for maemo-extras (although maemo.org Extras for diablo's Release file is not signed). Some questions: * The name of a domain is only to allow manipulation with hildon-application-manager-config? * What is the effect of two key elements against a domain entry? How would they have got there? * Any ideas where the maemo-extras one has come from? First step, I'd suggest would be a small rollout: * hildon-application-manager 1:2.1.xx-community (where xx 19) * hildon-application-manaer-l10n 5.1-community * osso-software-version-rx* 1:6.2009.nn-community I would lose the community suffix, actually. The osso-software-version-rx* package could get a display name that clearly spells out that this is not from Nokia. Fair enough. I suppose the only outstanding question is whether Nokia will push out one last SSU to include the maemo-community-updates package which correctly sets up the package domain for maemo.org Extras. Once we've got this sorted, I'm happy to produce and push the various packages (assistance always welcome, of course - especially with the osso-software-version-rx*). If we move quickly, we can work within the timescales Ryan's suggesting for the transition to the new package categories: http://lists.maemo.org/pipermail/maemo-developers/2009-April/054566.html Cheers, Andrew -- Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ Maemo Community Council chair ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo (specifically Application Manager if nothing else)
ext Andrew Flegg and...@bleb.org writes: So the key is the key. All of the entries on my N810 have *two* key elements per entry, and there's already one for maemo-extras (although maemo.org Extras for diablo's Release file is not signed). Some questions: * The name of a domain is only to allow manipulation with hildon-application-manager-config? That and for naming the files in /var/lib/hildon-application-manager/ that store the list of packages in each domain. * What is the effect of two key elements against a domain entry? How would they have got there? You can use either of the keys to sign the repo. The idea is that one of the keys is in use, and the other is in the safe. Then when the first key is compromised, you can roll-over to the second one and update the domain configuration to drop the first key. * Any ideas where the maemo-extras one has come from? The key? We made them together with the rest of the keys, to be prepared. The guys in charge of the repositories on maemo.org should be able to start signing with it right away, I think. (I.e., they have the private half of the first key somewhere ready on the server to be used.) Fair enough. I suppose the only outstanding question is whether Nokia will push out one last SSU to include the maemo-community-updates package which correctly sets up the package domain for maemo.org Extras. The only difference between Nokia doing it and the community doing it[1], is the little certified/ flag in the nokia-system package domain: when the community does it, there will be the usual legal warning to click through, when Nokia does it, the warning wont be shown. That's the only difference. I wouldn't plan with Nokia's support. [1] It always pains me when I have to put Nokia on one side, and the community on the other. I was hoping that Nokia would be a member of the community itself, but doesn't seem to happen. Once we've got this sorted, I'm happy to produce and push the various packages (assistance always welcome, of course - especially with the osso-software-version-rx*). I can make hildon-application-manager releases, of course, and give out write access to repos, as far as needed. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Community updates for diablo (specifically Application Manager if nothing else)
Hi, Following on from Marius Vollmer's comments in #3845[1] - New list of valid categories needs to be added to Application Manager [...], this is an attempt to start the discussion on how (and *if*) we can do as he outlines: Still, I think the best way forward is for the community to take ownership of Diablo, and to produce the next release. Matan Ziv-Av also started an earlier discussion on this: http://www.mail-archive.com/maemo-developers@maemo.org/msg17133.html Since the http://catalogue.tableteer.nokia.com/updates/diablo/ is, *cough*, stable now, it can be used as the basis for a community distribution. Depending on how brave we want to be, it is even feasible now to start offering new Diablo releases from Maemo Extras. I want to be this brave; if we can get notional sign-off from Quim - and it's technically achievable in an end-user friendly way. I think the following could work: - We start signing Diablo Maemo Extras. Some interesting practical questions: * How owns the key? The maemo.org debmaster (i.e. Jeremiah) is an obvious example; with copies also held by the council and the X-Fade? * AIUI, the only technical step here is to sign the Release file with the GPG key. - We put a maemo-community-archive-keyring package or something into Diablo Maemo Extras that contains the public key needed to verify the signature. It also contains a new package domain with a trust level of 600. The package domains are entirely Application Manager specific, IIRC? Does sort-weight in nokia-repository's postinst correspond to the trust level? Installing this package will configure the Application manager so that it allows updating OS packages from Maemo Extras. - We start putting new packages into Maemo Extras, such as the new Application manager. - We make release new osso-software-version meta packages or we improve the Application Manager to not need meta packages. First step, I'd suggest would be a small rollout: * hildon-application-manager 1:2.1.xx-community (where xx 19) * hildon-application-manaer-l10n 5.1-community * osso-software-version-rx* 1:6.2009.nn-community The only code change would be those from h-a-m with the grid view and the i18n fix. The l10n package would be built up from the strings in the package page[2]. If this works, we can then look to any future enhancements we want to make. If Diablo Maemo Extras doesn't seem to be the right place for this, any other repository will do as well, of course. I think it's the right place, since Extras is the key repository containing the packages. Outstanding questions which a more official Nokia position on would be good (Quim?): * Is there _any_ chance of getting maemo-community-archive-keyring shipped through Tableteer, and so being more actively pushed out to users as part of an SSU? * If we are careful to not change the fundamental behaviour of the system, are Nokia happy with the community pushing out individual updates to system components via SSU, using the above mechanism? In particular, I don't think we should use this power (if able to us) to bulk-update everyone to Mer in about 6 months' time ;-) Cheers, Andrew [1] https://bugs.maemo.org/show_bug.cgi?id=3845#c11 [2] http://wiki.maemo.org/Task:Package_categories#Translations -- Andrew Flegg -- mailto:and...@bleb.org | http://www.bleb.org/ Maemo Community Council chair ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Community updates for diablo (specifically Application Manager if nothing else)
ext Andrew Flegg and...@bleb.org writes: Marius wrote: I think the following could work: - We start signing Diablo Maemo Extras. [...] * AIUI, the only technical step here is to sign the Release file with the GPG key. Yes. - We put a maemo-community-archive-keyring package or something into Diablo Maemo Extras that contains the public key needed to verify the signature. It also contains a new package domain with a trust level of 600. The package domains are entirely Application Manager specific, IIRC? Yes. Does sort-weight in nokia-repository's postinst correspond to the trust level? No, not at all. The sort-weight is used to sort the catalogues when displaying them in the UI. Package domains are 'orthogonal' to catalogues and repositories. They are connected by the signature of the Release file. The AM looks at the keys that have been used to sign the Release file and associates each package with a package domain. Package domains are configured in /etc/hildon-application-manager/domains. You will find the trust level in there, among other things. See here http://hildon-app-mgr.garage.maemo.org/repos-stable.html for a bit more. First step, I'd suggest would be a small rollout: * hildon-application-manager 1:2.1.xx-community (where xx 19) * hildon-application-manaer-l10n 5.1-community * osso-software-version-rx* 1:6.2009.nn-community I would lose the community suffix, actually. The osso-software-version-rx* package could get a display name that clearly spells out that this is not from Nokia. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
