On Mon, Jul 28, 2014 at 09:47:14PM +0100, Dominic Hargreaves wrote: > On Sat, May 31, 2014 at 10:25:44PM +0300, Niko Tyni wrote: > > There's a couple of hardcoded instances of /usr/lib/perl5 in debhelper > > that are soon going to be outdated as $Config{vendorarch} will change > > with Perl 5.20.0. See #748380. > > > > While at it, the attached patch also changes instances > > of /usr/share/perl5 to expand $Config{vendorlib}, > > although that is not expected to change (and would be > > rather hard to change without arch:all binNMUs.) > We planning an upload to sid of perl 5.20 on around 12th August, at > which point this bug will become more exposed. It would be nice (but > not essential) to get this patch included in debhelper before then; > do you have any plans to do so or do you need any more input from the > perl team?
Ping? For clarity: the main effect of this bug is that dh_fixperms will not fix permissions of *.pm files under $Config{vendorarch} (currently /usr/lib/perl5) anymore. (A secondary effect is that dh_perl will not remove empty directories under $Config{vendorarch}.) Given that all the packages having files under $Config{vendorarch} will be rebuilt with the Perl 5.20 transition hopefully next week, this will bite all of them that are currently relying on this functionality in one go. I went through my build logs and found 18 packages containing files with non-standard permissions under $Config{vendorarch} when built with perl_5.20.0-1: exactimage_0.8.9-6 libapache-authenhook-perl_2.00-04+pristine-5 libapache-db-perl_0.14-4 libauthen-sasl-cyrus-perl_0.13-server-10 libclone-perl_0.37-1 libdate-simple-perl_3.0300-1 libfilesys-smbclient-perl_3.2-2 libforks-perl_0.34-2 libfuse-perl_0.16.1-1 libmath-bigint-gmp-perl_1.38-1 libmath-int64-perl_0.30-2 libnet-arp-perl_1.0.8-1 libnet-idn-encode-perl_2.200-1 libsgml-parser-opensp-perl_0.994-3 libtest-leaktrace-perl_0.14-2 libtfbs-perl_0.6.0+dfsg-1 libtk-tablematrix-perl_1.23-6 libxml-bare-perl_0.53-1 (Changing usr/share/perl5 to $Config{vendorlib} in my patch is not necessary for this transition. It's sort of overkill but shouldn't hurt either.) -- Niko Tyni nt...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org