On Mon, Nov 12, 2012 at 02:15:48PM +0000, Adam D. Barratt wrote: > On Sat, 2012-10-27 at 20:08 +0200, Kurt Roeckx wrote: > > So Neil told me on IRC to just fix #684825 via t-p-u using the patch > > that's in that bug report. > > > > I looked in to that and found that to due multi-arch changes in > > glibc I now run into #691612. > > > > So if I want to fix it via t-p-u I would also need to backport the > > multi-arch changes. > > Looking at the diff, are there any changes required outside of the > --libdir setting in debian/rules and the path changes in *.install?
As far as I know the changed for multiarch would require: - newer debhelper, new compat level - control file changes - *.install changes - the --libdir option to configure > > The original patch for that is in #657139, > > but the patch like it's in that bug report is broken. > > That bug is currently assigned to eglibc. What's the status there - does > unstable's elfutils function correctly wrt multi-arch, or are there > further changes needed on the libc side? The bug that's assigned to libc is #632281. I don't know about the status there. If we get a multiarch version of elfutils in testing, there is no need to change libc (for me). But I think it would be good in general that it would look at both the non-multiarch and multiarch path. The libc code in testing/unstable will only look at the multi-arch path. So the elfutils in testing doesn't work, but the elfutils in unstable does work. Kurt -- To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121112145220.ga25...@roeckx.be
