Hi! On Sat, 2015-04-04 at 08:05:36 +0200, Niels Thykier wrote: > On 2015-03-24 06:52, Niels Thykier wrote: > > Package: dpkg > > Version: 1.17.24 > > Severity: normal
> > The following warnings were seen during the debian-installer build[1][2]: > > > > """ > > dpkg-distaddfile debian-installer-images_20150324_ppc64el.tar.gz > > raw-installer - > > dpkg-distaddfile: warning: File::FcntlLock not available; using flock which > > is not NFS-safe > > dpkg-genchanges -B -mppc64el Build Daemon (ppc64el-unicamp-01) > > <buildd_ppc64el-ppc64el-unicamp...@buildd.debian.org> > > >../debian-installer_20150324_ppc64el.changes > > dpkg-genchanges: binary-only arch-specific upload (source code and > > arch-indep packages not included) > > Use of uninitialized value $b in string eq at /usr/share/perl5/Dpkg/Arch.pm > > line 399. > > Use of uninitialized value $arch in pattern match (m//) at > > /usr/share/perl5/Dpkg/Arch.pm line 335. > > Use of uninitialized value $arch in hash element at > > /usr/share/perl5/Dpkg/Arch.pm line 340. > > dpkg-source --after-build debian-installer-20150324 > > dpkg-buildpackage: binary-only upload (no source included) > > > > [...] > > > > """ > Based on the code, all 3 warning is probably coming from a call to > debarch_eq where the second parameter is undef (it calls another sub > with that undef argument, which name I forgot now, but it would emit two > those warnings in that case). > Sadly, I do not yet know which of the call sites causes this issue. I fixed this some time ago, I forgot to mention it here, sorry. Unfortunately it's still entangled in my "next" branch of doom, with aroun 90 patches to rereview and flush. :/ In any case will be fixed in 1.18.0. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
