[sbopkg-users] Weird google-chrome Related Error During Update

[Chess Griffin]

* Mauro Giachero <mauro.giachero at gmail.com> [2010-02-17 13:57:02]:

> On Wed, Feb 17, 2010 at 4:32 AM, alkos333 <me at alkos333.net> wrote:
> 
> > The subject pretty much speaks for itself.  This is what I see on the
> > screen:  http://bit.ly/an9BfD
> >
> 
> This was unexpected -- the script requires the source tarball to
> determine the chrome version.  I can't think about any sane way to
> address this. The only workaround I see is to trap the error, silence
> the messages and fall back to trusting the .info file for the version
> number. Maybe log something about the event.  Does that look
> reasonable?
> 

Yes, that VERSION line in the SlackBuild is causing the issue and some
kind of workaround like you describe is probably the only solution.  If
I am understanding the SlackBuild script correctly, the true version of
Google Chrome changes daily.  So, from sbopkg's standpoint, the
"version" in the repo will always be different.  If we ignore this
VERSION line, then the repo version will be stuck at whatever is
hardcoded into the .info file, which means the user's version will likey
always show up as a 'installed version is newer than repo' which we might
just have to live with.

-- 
Chess Griffin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://sbopkg.org/pipermail/sbopkg-users/attachments/20100217/daaf0cba/attachment.sig>