lubuntu-qa team mailing list archive

[Phill Whiteside <PhillW@xxxxxxxxxx>]

Thanks boss,

I'm just downloading a 'clean' 12.10 iso to run in VM so I can just check
to see if update in Quantal is pulling in the newer Chromium, or it is the
PPA. Latest from that dev PPA is
chromium-browser_23.0.1271.1~svn20120922r157674-0ubuntu1 So, there is
deffinatley a newer one available. Is this 'newer' one that has the ubuntu
'tag' on it that needs forwarding to be SRU'd?

As Far as I can check, the one in Lubuntu 12.10 is
22.0.1229.94~r161065-0ubuntu1
I don't know what the 'svn' and 'r' bits mean, I just go off the 1st part
for version / sub-version number.

Sorry to bother you, I'm trying to get my head around how this numbering
sequence works and the meaning of the ubuntu1 tag on them.

Regards,

Phill.


On 5 November 2012 17:56, Julien Lavergne <gilir@xxxxxxxxxx> wrote:

> Le 05/11/2012 01:08, Phill Whiteside a écrit :
>
>  From memory, most of the updates I see for Chromium are not 'feature'
>> updates. The ones I see are security updates for when vulnerabilities have
>> been found and are available? I'm not sure how such upstream patches are
>> applied for, say, FireFox that are released by mozilla foundation?
>>
> There are "features" updates, but it's tricky. Both Firefox and Chromium
> do release with include both security updates, and features updates. In
> this case, you can't just take the security items and package them, you are
> forced to do the entire update. That's why new versions of Firefox and
> Chromium are SRUed, even if it's a new release. It's an exception in the
> SRU process.
>
>
>  You know much more about this area, are CVE updates normal SRU's or
>> security team driven?
>>
> Security updates are driven by the security team, but it's only for
> packages in main. In universe (for example, Chromium), they do what they
> can (no guaranty).
>
> Regards,
> Julien Lavergne
>



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