From @jkeenan

[This ticket was originally create in 2010 as https://rt.cpan.org/Ticket/Display.html?id=57046.  Since ExtUtils-Manifest is now primarily maintained by Perl 5 Porters, I am moving the issue to rt.perl.org. --jkeenan]

I've got a continuous integration server doing builds of distributions with automatically created MANIFEST files. I don't want to see all the messages about files being added to the MANIFEST files, so I set the PERL_MM_MANIFEST_VERBOSE environment variable to 0. However, this means that, if the server upgrades its copy of EU​::Manifest during a build, the tests fail.

-- perl at galumph dot com

From @jkeenan

Summary of my perl5 (revision 5 version 21 subversion 3) configuration​:
  Commit id​: ce5b0b8
  Platform​:
  osname=linux, osvers=3.13.0-32-generic, archname=x86_64-linux
  uname='linux zareason 3.13.0-32-generic #57-ubuntu smp tue jul 15 03​:51​:08 utc 2014 x86_64 x86_64 x86_64 gnulinux '
  config_args='-des -Dusedevel'
  hint=recommended, useposix=true, d_sigaction=define
  useithreads=undef, usemultiplicity=undef
  use64bitint=define, use64bitall=define, uselongdouble=undef
  usemymalloc=n, bincompat5005=undef
  Compiler​:
  cc='cc', ccflags ='-fwrapv -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64',
  optimize='-O2',
  cppflags='-fwrapv -fno-strict-aliasing -pipe -fstack-protector -I/usr/local/include'
  ccversion='', gccversion='4.8.2', gccosandvers=''
  intsize=4, longsize=8, ptrsize=8, doublesize=8, byteorder=12345678
  d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=16
  ivtype='long', ivsize=8, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8
  alignbytes=8, prototype=define
  Linker and Libraries​:
  ld='cc', ldflags =' -fstack-protector -L/usr/local/lib'
  libpth=/usr/local/lib /usr/lib/gcc/x86_64-linux-gnu/4.8/include-fixed /usr/include/x86_64-linux-gnu /usr/lib /lib/x86_64-linux-gnu /lib/../lib /usr/lib/x86_64-linux-gnu /usr/lib/../lib /lib
  libs=-lnsl -ldl -lm -lcrypt -lutil -lc
  perllibs=-lnsl -ldl -lm -lcrypt -lutil -lc
  libc=libc-2.19.so, so=so, useshrplib=false, libperl=libperl.a
  gnulibc_version='2.19'
  Dynamic Linking​:
  dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-Wl,-E'
  cccdlflags='-fPIC', lddlflags='-shared -O2 -L/usr/local/lib -fstack-protector'

Characteristics of this binary (from libperl)​:
  Compile-time options​: HAS_TIMES PERLIO_LAYERS PERL_DONT_CREATE_GVSV
  PERL_HASH_FUNC_ONE_AT_A_TIME_HARD PERL_MALLOC_WRAP
  PERL_NEW_COPY_ON_WRITE PERL_PRESERVE_IVUV
  PERL_USE_DEVEL USE_64_BIT_ALL USE_64_BIT_INT
  USE_LARGE_FILES USE_LOCALE USE_LOCALE_COLLATE
  USE_LOCALE_CTYPE USE_LOCALE_NUMERIC USE_LOCALE_TIME
  USE_PERLIO USE_PERL_ATOF
  Built under linux
  Compiled at Jul 27 2014 17​:53​:58
  %ENV​:
  PERL5LIB="/home/jkeenan/perl5/lib/perl5"
  PERLBREW_BASHRC_VERSION="0.67"
  PERLBREW_HOME="/home/jkeenan/.perlbrew"
  PERLBREW_MANPATH="/home/jkeenan/perl5/perlbrew/perls/perl-5.20.0/man"
  PERLBREW_PATH="/home/jkeenan/perl5/perlbrew/bin​:/home/jkeenan/perl5/perlbrew/perls/perl-5.20.0/bin"
  PERLBREW_PERL="perl-5.20.0"
  PERLBREW_ROOT="/home/jkeenan/perl5/perlbrew"
  PERLBREW_VERSION="0.67"
  PERL_LOCAL_LIB_ROOT="/home/jkeenan/perl5"
  PERL_MB_OPT="--install_base "/home/jkeenan/perl5""
  PERL_MM_OPT="INSTALL_BASE=/home/jkeenan/perl5"
  PERL_WORKDIR="gitwork/perl"
  @​INC​:
  lib
  /home/jkeenan/perl5/lib/perl5/x86_64-linux
  /home/jkeenan/perl5/lib/perl5
  /usr/local/lib/perl5/site_perl/5.21.3/x86_64-linux
  /usr/local/lib/perl5/site_perl/5.21.3
  /usr/local/lib/perl5/5.21.3/x86_64-linux
  /usr/local/lib/perl5/5.21.3
  .

From @jkeenan

Elliot wrote in 2010​:

I've got a continuous integration server doing builds of distributions
with automatically created MANIFEST files. I don't want to see all the
messages about files being added to the MANIFEST files, so I set the
PERL_MM_MANIFEST_VERBOSE environment variable to 0. However, this
means that, if the server upgrades its copy of EU​::Manifest during a
build, the tests fail.

-- perl at galumph dot com

1. Elliott, is this still a concern for you?

2. Which tests, specifically, are failing?

Thank you very much.
Jim Keenan

The RT System itself - Status changed from 'new' to 'open'

From perl@galumph.com

On 7/28/14, 9​:20 PM, James E Keenan via RT wrote​:

1. Elliott, is this still a concern for you?

No.

From @jkeenan

On Wed Jul 30 22​:25​:31 2014, perl@​galumph.com wrote​:

On 7/28/14, 9​:20 PM, James E Keenan via RT wrote​:

1. Elliott, is this still a concern for you?

No.

Closing as per reply from OP.

@jkeenan - Status changed from 'open' to 'resolved'