| 2010-12-07 16:12:38 |
Jamie Strandboge |
description |
Binary package hint: chromium-codecs-ffmpeg
for i in chromium-codecs-ffmpeg_*deb ; do echo $i:; lintian $i; done
chromium-codecs-ffmpeg_0.5+svn20100406r43776+43984+43918-0ubuntu1_amd64.deb:
chromium-codecs-ffmpeg_0.5+svn20100406r43776+43984+43918-0ubuntu1_i386.deb:
E: chromium-codecs-ffmpeg: shlib-with-non-pic-code usr/lib/chromium-browser/libffmpegsumo.so
chromium-codecs-ffmpeg_0.6+svn20100904r58574+58998-0ubuntu0.10.04.1_amd64.deb:
chromium-codecs-ffmpeg_0.6+svn20100904r58574+58998-0ubuntu0.10.04.1_i386.deb:
E: chromium-codecs-ffmpeg: shlib-with-non-pic-code usr/lib/chromium-browser/libffmpegsumo.so
chromium-codecs-ffmpeg_0.6+svn20100904r58574+58998-0ubuntu1_amd64.deb:
chromium-codecs-ffmpeg_0.6+svn20100904r58574+58998-0ubuntu1_i386.deb:
E: chromium-codecs-ffmpeg: shlib-with-non-pic-code usr/lib/chromium-browser/libffmpegsumo.so
This is in violation of section 10.2 of the Ubuntu Policy manual (http://people.canonical.com/~cjwatson/ubuntu-policy/policy.html/ch-files.html#s-libraries):
"If the package is _architecture: any_, then the shared library compilation and linking flags must have `-fPIC', or the package shall not build on some of the supported architectures. Any exception to this rule must be discussed on the mailing list ubuntu-devel@lists.ubuntu.com, and a rough consensus obtained. The reasons for not compiling with `-fPIC' flag must be recorded in the file `README.Debian', and care must be taken to either restrict the architecture or arrange for `-fPIC' to be used on architectures where it is required."
As discussed in the mythtv thread on ubuntu-devel@, this most likely just needs an override and supporting documentation in README.Debian since it is a fork of ffmpeg, and that is what is done in the ffmpeg package. This should be done for all releases, but let's only update Lucid and Maverick if this package is getting another update (eg, security or SRU). |
Binary package hint: chromium-codecs-ffmpeg
for i in chromium-codecs-ffmpeg_*deb ; do echo $i:; lintian $i; done
chromium-codecs-ffmpeg_0.5+svn20100406r43776+43984+43918-0ubuntu1_amd64.deb:
chromium-codecs-ffmpeg_0.5+svn20100406r43776+43984+43918-0ubuntu1_i386.deb:
E: chromium-codecs-ffmpeg: shlib-with-non-pic-code usr/lib/chromium-browser/libffmpegsumo.so
chromium-codecs-ffmpeg_0.6+svn20100904r58574+58998-0ubuntu0.10.04.1_amd64.deb:
chromium-codecs-ffmpeg_0.6+svn20100904r58574+58998-0ubuntu0.10.04.1_i386.deb:
E: chromium-codecs-ffmpeg: shlib-with-non-pic-code usr/lib/chromium-browser/libffmpegsumo.so
chromium-codecs-ffmpeg_0.6+svn20100904r58574+58998-0ubuntu1_amd64.deb:
chromium-codecs-ffmpeg_0.6+svn20100904r58574+58998-0ubuntu1_i386.deb:
E: chromium-codecs-ffmpeg: shlib-with-non-pic-code usr/lib/chromium-browser/libffmpegsumo.so
This is in violation of section 10.2 of the Ubuntu Policy manual (http://people.canonical.com/~cjwatson/ubuntu-policy/policy.html/ch-files.html#s-libraries):
"If the package is _architecture: any_, then the shared library compilation and linking flags must have `-fPIC', or the package shall not build on some of the supported architectures. Any exception to this rule must be discussed on the mailing list ubuntu-devel@lists.ubuntu.com, and a rough consensus obtained. The reasons for not compiling with `-fPIC' flag must be recorded in the file `README.Debian', and care must be taken to either restrict the architecture or arrange for `-fPIC' to be used on architectures where it is required."
As discussed in the mythtv thread on ubuntu-devel@ and bug #684941, this most likely just needs an override and supporting documentation in README.Debian since it is a fork of ffmpeg, and that is what is done in the ffmpeg package. This should be done for all releases, but let's only update Lucid and Maverick if this package is getting another update (eg, security or SRU).
|
|
