Bug#329842: xlibmesa-dri: Security update supplies unstripped modules on amd64
reassign 329842 security.debian.org
tags 329842 + wontfix confirmed
kthxbye
On 10421 March 1977, Helge Kreutzmann wrote:
> when I wanted to install the security update I was shocked that it
> wanted 73,4 MB more space than the current version. To check if this
> was a problem on the buildd, I downloaded the source and rebuild
> XFree86 (which required a local build of glide, which was not
> available for amd64 previously). The result was the same.
Well, yes, known. As written in the debian-amd64 list, where you asked
first, its an error from the buildd.
The reason is, as you found out (you really built it completly
yourself? There is *NO* public buildd-log for this security build), the
strip doesnt work.
Its an interaction between dh_strip and an XFS filesystem, causing the
errors you see.
The buildd is fixed to only use ext3 from now on, so it shouldnt happen
again in the future (and from all security builds that got build on
this host this is the only one having this).
The solution, until another X security build comes around is to
manually strip the files after installation, it doesnt hurt in any
other way.
Run something like
dpkg -c xlibmesa-dri_4.3.0.dfsg.1-14sarge1_amd64.deb | grep X11R6|grep \
-v drw|awk '{print $6}'|sed s/^\.//|xargs strip
Ive reassigned this bug to the right place after talking with Joey
Schulze, which is security.debian.org.
--
bye Joerg
Reply to: