I don't see that we have any option. Acked.
--
chromium update: 5.0.375.127 - 6.0.472.53
https://bugs.launchpad.net/bugs/628924
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Copied to lucid-security and lucid-updates.
** Changed in: gyp (Ubuntu Lucid)
Status: Fix Committed = Fix Released
** Changed in: libvpx (Ubuntu Lucid)
Status: Fix Committed = Fix Released
** Changed in: chromium-codecs-ffmpeg (Ubuntu Lucid)
Status: Fix Committed = Fix
chromium-codecs-ffmpeg 0.6+svn20100904r58574+58998-0ubuntu0.10.04.1
uploaded to lucid-proposed, which fixes the arm FTBFS.
--
chromium update: 5.0.375.127 - 6.0.472.53
https://bugs.launchpad.net/bugs/628924
You received this bug notification because you are a member of Ubuntu
Bugs, which is
chromium-codecs-ffmpeg tested with www.youtube.com/watch?v=_hTiRnqnvDs
(html5 green lantern trailer, see www.webmproject.org/users/).
$ apt-cache policy chromium-codecs-ffmpeg-extra
chromium-codecs-ffmpeg-extra:
Installed: 0.6+svn20100904r58574+58998-0ubuntu0.10.04.1
Candidate:
Fabien provided updated chromium-codecs-ffmpeg packages with ARM fixes
which are now building in the security-proposed PPA. When done building,
I will move them to lucid-proposed. Once these are verified I think we
should copy all of them to lucid-security and lucid-updates immediately
(since
As mentioned, this works well here, however unlike previous updates this
will break ARM. It is my opinion that we should push this to -security
and -updates regardless, since there are some rather important fixes in
here. Due to the nature of the update, I am uncomfortable pushing to
-security
Tested on amd64 with QRT and it works as well as the previous version.
--
chromium update: 5.0.375.127 - 6.0.472.53
https://bugs.launchpad.net/bugs/628924
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
chromium-codecs-ffmpeg FTBFS on lucid and maverick, which is a
regression over chromium 5.0.
--
chromium update: 5.0.375.127 - 6.0.472.53
https://bugs.launchpad.net/bugs/628924
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
@Jamie
#6: i never asked for it, see the original description of this bug.
#7: i didn't change the get-orig-source rule recently. it's probably
possible to go through all the deps once again and prune the tree a
little bit more, but as it is, each time upstream adopts a new project
in its tree,
Pocket copied chromium-browser, gyp, chromium-codecs-ffmpeg, and libvpx
to proposed. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
To ubuntu-sru: if this passes the verification
** Branch linked: lp:ubuntu/lucid-proposed/libvpx
--
chromium update: 5.0.375.127 - 6.0.472.53
https://bugs.launchpad.net/bugs/628924
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Copied everything to lucid-proposed even though chromium-codecs-ffmpeg
FTBFS on armel. Idea is that at a minimum, we can get testing on i386
amd64 while upstream fixes chromium-codecs-ffmpeg.
--
chromium update: 5.0.375.127 - 6.0.472.53
https://bugs.launchpad.net/bugs/628924
You received this
** Branch linked: lp:ubuntu/lucid-proposed/gyp
** Branch linked: lp:ubuntu/lucid-proposed/chromium-codecs-ffmpeg
--
chromium update: 5.0.375.127 - 6.0.472.53
https://bugs.launchpad.net/bugs/628924
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Fabien pointed out the arm FTBFS is
http://code.google.com/p/chromium/issues/detail?id=49617.
** Bug watch added: code.google.com/p/chromium/issues #49617
http://code.google.com/p/chromium/issues/detail?id=49617
--
chromium update: 5.0.375.127 - 6.0.472.53
** Also affects: chromium-browser (Ubuntu Lucid)
Importance: Undecided
Status: New
** Also affects: chromium-browser (Ubuntu Maverick)
Importance: High
Assignee: Fabien Tassin (fta)
Status: In Progress
** Changed in: chromium-browser (Ubuntu Lucid)
Status: New =
** Description changed:
Binary package hint: chromium-browser
Upstream just released a major update of Chromium (incl several security
fixes). It's needed in both maverick and lucid.
http://googlechromereleases.blogspot.com/2010/09/stable-and-beta-
channel-updates.html
I'm
All done.
For maverick, everything is waiting for approval.
For lucid-security, it's all there:
http://people.ubuntu.com/~fta/chromium/6.0.472.53~r57914-0ubuntu0.10.04.1/
it's also available in both the Beta and Stable PPAs.
--
chromium update: 5.0.375.127 - 6.0.472.53
** Also affects: gyp (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libvpx (Ubuntu)
Importance: Undecided
Status: New
** Also affects: chromium-codecs-ffmpeg (Ubuntu)
Importance: Undecided
Status: New
--
chromium update: 5.0.375.127 - 6.0.472.53
Uploaded gyp, libvpx, chromium-codec-ffmpeg and chromium-browser for
lucid to ubuntu-security-proposed.
** Tags added: security-verification
** Changed in: gyp (Ubuntu Lucid)
Status: New = In Progress
** Changed in: gyp (Ubuntu Lucid)
Assignee: (unassigned) = Fabien Tassin (fta)
**
** This bug has been flagged as a security vulnerability
--
chromium update: 5.0.375.127 - 6.0.472.53
https://bugs.launchpad.net/bugs/628924
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package chromium-browser -
6.0.472.53~r57914-0ubuntu1
---
chromium-browser (6.0.472.53~r57914-0ubuntu1) maverick; urgency=low
* New upstream release from the Stable Channel (LP: #628924)
This release fixes the following security issues:
- [34414]
This bug was fixed in the package chromium-codecs-ffmpeg -
0.6+svn20100811r55740+56137-0ubuntu1
---
chromium-codecs-ffmpeg (0.6+svn20100811r55740+56137-0ubuntu1) maverick;
urgency=low
* New upstream snapshot (LP: #628924)
* Drop the sse2 patch, it has been applied upstream, and
This bug was fixed in the package gyp - 0.1~svn840-0ubuntu1
---
gyp (0.1~svn840-0ubuntu1) maverick; urgency=low
* New upstream snapshot (LP: #628924)
-- Fabien Tassin f...@ubuntu.com Thu, 02 Sep 2010 17:03:41 +0200
** Branch linked: lp:ubuntu/chromium-codecs-ffmpeg
**
** Branch linked: lp:ubuntu/gyp
--
chromium update: 5.0.375.127 - 6.0.472.53
https://bugs.launchpad.net/bugs/628924
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Marking libvpx on Maverick as Invalid-- it is already in Maverick.
** Changed in: libvpx (Ubuntu Maverick)
Status: New = Invalid
--
chromium update: 5.0.375.127 - 6.0.472.53
https://bugs.launchpad.net/bugs/628924
You received this bug notification because you are a member of Ubuntu
Bugs,
Not that there is much choice in the matter due to upstream's release
practices, but it should at least be mentioned that the size of the
source tarball for chromium-browser_5.0.375.127~r55887.orig.tar.gz was
93M and for chromium-browser_6.0.472.53~r57914.orig.tar.gz it is a quite
large 146M. This
26 matches
Mail list logo
