The quickest solution would be to remove "--enable-vty-tests" from distcheck variables but I do not see how they are populated? I've reproduced it with osmo-pcu but not with openbsc - I wonder what's the difference between how distcheck is run for both.
On 04/13/2016 12:49 PM, Holger Freyther wrote: >> On 13 Apr 2016, at 04:10, Max <[email protected]> wrote: >> > Hi, > >> Not directly - the error is not triggered from the code I've added. But >> it could be that my code somehow changed/not changed metadata in some >> corner case. I'm unable to reproduce this locally - is there way to get >> file details from jenkins? Permission, owner, xattr etc from both target >> and destination of the copy and upper folders? > well, the responsibility is with you. Have you looked at the console output > and when it happens? > > It happens with "make: *** [distcheck] Error 1". Which means the source > directory will be checked out read-only, which means the files you copy are > read-only. I would be surprised if > > DISTCHECK_CONFIGURE_FLAGS=--enable-sysmocom-bts=no --enable-sysmocom-dsp=no > --enable-vty-tests AM_DISTCHECK_CONFIGURE_FLAGS=--enable-sysmocom-bts=no > --enable-sysmocom-dsp=no --enable-vty-tests > PKG_CONFIG_PATH=/home/builder/source/workspace/osmo-pcu/label/linux_i386_debian_squeeze/sysmobts/no/sysmodsp/no/deps/install/lib/pkgconfig > > LD_LIBRARY_PATH=/home/builder/source/workspace/osmo-pcu/label/linux_i386_debian_squeeze/sysmobts/no/sysmodsp/no/deps/install/lib > make distcheck > > doesn't reproduce the issue for you. > > holger -- Max Suraev <[email protected]> http://www.sysmocom.de/ ======================================================================= * sysmocom - systems for mobile communications GmbH * Alt-Moabit 93 * 10559 Berlin, Germany * Sitz / Registered office: Berlin, HRB 134158 B * Geschaeftsfuehrer / Managing Directors: Holger Freyther, Harald Welte
