On 01/04/2012 12:44 AM, Michael Gilbert wrote: > Which settings in particular do you know of that make the chromium > backport work?
haven't you looked at the git repository[0]? e.g. 'git diff debian-wheezy..progress-artax-backports' gives all the changes. citing from changelog: ---snip--- chromium-browser (16.0.912.63~r113337-1~artax1) artax; urgency=low * Uploading to artax, remaining changes: - Updating maintainer and uploaders fields. - Updating vcs fields. - Adding bugs field. - Always building for debian-squeeze rather than autodetecting distribution, vendor and release number with lsb_release. - Reverting use of binutils-gold to fix FTBFS. - Reverting changes for cups (>= 1.5). - Reverting changes to use system ffmpeg. - Reverting changes for multiarch. - Updating chromium install file for upstreams ffmpegsumo_nolink removal. -- Daniel Baumann <daniel.baum...@progress-linux.org> Mon, 02 Jan 2012 07:17:39 +0100 ---snap--- [0] http://vcs.progress-linux.org/?p=packages/chromium-browser.git -- Address: Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org