lubuntu-qa team mailing list archive

[Phill Whiteside <PhillW@xxxxxxxxxx>]

apologies for anyone who gets this twice, I sent it from the wrong email
account!

Phill.

---------- Forwarded message ----------
From: Phill Whiteside <phillw@xxxxxxxxxxx>
Date: 6 November 2012 01:21
Subject: Chromium Updates
To: micahg@xxxxxxxxxx
Cc: Julien Lavergne <gilir@xxxxxxxxxx>, lubuntu-qa@xxxxxxxxxxxxxxxxxxx


Hi,

it is apparent that the SRU / Updates of Chromium have stalled. This does
directly affect Lubuntu as we ship it as default. Julien (gilir) has given
me some pointers as to how to get SRU updates done, but I see that at [1]
it has a tech-board exception. You voiced concern at using alex's PPA.


I had contacted Micah Gersten <micahg@xxxxxxxxxx> some time ago about
> involving my PPA into Ubuntu release. He said that he is not comfortable
> about using non-ubuntu dev packages in Chromium repositories, but he could
> use my scripts.


I had a quick chat with duty SRU person earlier and he suggested I contact
you directly.

Yes, I'm new to SRU, but am also the Lubuntu QA liason person and would
really like to help out. Julien (gilir) stated:

For stable releases, we should not use any PPA, it should be directly in
> the repositories.
> In the past, stable releases was uploaded in all supported releases.
> Recently, nobody maintains chromium anymore in Ubuntu. So, I think it
> would be very useful if the stable releases can be packaged and propose
> as a SRU [1]. I'm sure it will be easy to find someone to upload them if
> it's well prepared.
> I can provide some guidance if it's necessary, and I think it's a very
> good way to contribute to Ubuntu.
> Regards,
> Julien Lavergne
> [1] https://wiki.ubuntu.com/StableReleaseUpdates



If you could spend a little time to let me know what needs doing for the
updates to be accepted I'd be happy to take on the 'donkey work' of having
these mix of security & feature fixes set up for approval. As with, e.g.
firefox, is the fact that it works on current enough to ask that they be
tested by the lubuntu-qa people and then get 'back ported' or is that a
totally different thing? On this, I'm asking what would the correct method
of resolving this bug [2]?  I'm on Version 23.0.1271.1 Ubuntu 12.10 (157674)

Regards,

Phill.
1. https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions
2. https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/608538

-- 
https://wiki.ubuntu.com/phillw

-- 
<https://wiki.ubuntu.com/phillw>https://wiki.ubuntu.com/phillw