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

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

2010/5/3 Lucas Maneos <maemo@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

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.

> 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

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.

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-bounces@maemo.org
[mailto:maemo-developers-bounces@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.

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)

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.

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)