Re: [sane-devel] [janitorial] Error @ git push
Hi Rolf,
Thanks for reminding everyone of the issue[1], :-). The short answer is
that there is nothing to worry really about. Everything should be fine.
For the longer answer, see my comments below.
[1]
https://lists.alioth.debian.org/pipermail/sane-devel/2015-December/034213.html
Rolf Bensch writes:
> Hi Olaf,
>
> My last git push produced this output:
>
> Versende nach
> git+ssh://roben-gu...@git.debian.org/git/sane/sane-backends.git
> remote: Sending notification emails to:
> sane-com...@lists.alioth.debian.org
> remote: Aktualisiere d94c29a..3258b70
> remote: Fast-forward
> remote: backend/hp3500.c| 2 ++
> remote: backend/plustek-pp_scan.h | 6 +-
> remote: configure | 2 +-
> remote: configure.ac| 2 +-
> remote: doc/descriptions/pixma.desc | 4 ++--
> remote: include/sane/config.h.in| 3 ---
Now that's odd! You seem to be sending two commits of mine with your
change to pixma.desc as well.
Maybe your local master was behind origin/master when you pushed?
Anyway, your change to pixma.desc triggered a rebuild of the supported
device lists on the website. Due to my changes to configure{,.ac} that
rebuild decided it needs to reconfigure the checked out source tree (on
Alioth) and do so like
> remote: 6 files changed, 7 insertions(+), 12 deletions(-)
> remote: cd .. && make am--refresh
> remote: make[1]: Entering directory
> `/var/lib/gforge/chroot/home/groups/sane/sane-backends-lists-git'
> remote: /bin/bash ./config.status --recheck
You can see it runs a ./config.status script (which remembers the
options used when ./configure was run) and tells it to --recheck.
> [...]
Near the very end, the ./config.status script updates itself with any
new findings (so you can do a ./config.status *without* --recheck'ing
real fast) and tries to set execute permissions on the script. The
latter fails because the script is owned by kitno-guest and the update
is run by roben-guest.
# The code that does this is courtesy of autoconf so it is not trivial
# to fix this in a persistent way :-(
> remote: configure: creating ./config.status
> remote: chmod: changing permissions of `./config.status': Operation not
> permitted
> remote: configure: error: write failure creating ./config.status
This is not a problem because the script already has the permissions it
is trying to set.
> I've never seen the checking stuff before.
The configure{,.ac} scripts don't change all that frequently ;-)
I see the checking quite a bit when fiddling with autofoo stuff. As
long as it only complains about not being able to set permissions on
./config.status things should be fine.
Hope this helps,
--
Olaf Meeuwissen, LPIC-2FSF Associate Member since 2004-01-27
GnuPG key: F84A2DD9/B3C0 2F47 EA19 64F4 9F13 F43E B8A4 A88A F84A 2DD9
Support Free Softwarehttps://my.fsf.org/donate
Join the Free Software Foundation https://my.fsf.org/join
--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org
[sane-devel] [janitorial] Error @ git push
Hi Olaf, My last git push produced this output: Versende nach git+ssh://roben-gu...@git.debian.org/git/sane/sane-backends.git remote: Sending notification emails to: sane-com...@lists.alioth.debian.org remote: Aktualisiere d94c29a..3258b70 remote: Fast-forward remote: backend/hp3500.c| 2 ++ remote: backend/plustek-pp_scan.h | 6 +- remote: configure | 2 +- remote: configure.ac| 2 +- remote: doc/descriptions/pixma.desc | 4 ++-- remote: include/sane/config.h.in| 3 --- remote: 6 files changed, 7 insertions(+), 12 deletions(-) remote: cd .. && make am--refresh remote: make[1]: Entering directory `/var/lib/gforge/chroot/home/groups/sane/sane-backends-lists-git' remote: /bin/bash ./config.status --recheck remote: running CONFIG_SHELL=/bin/bash /bin/bash ./configure --no-create --no-recursion remote: checking for a BSD-compatible install... /usr/bin/install -c remote: checking whether build environment is sane... yes remote: checking for a thread-safe mkdir -p... /bin/mkdir -p remote: checking for gawk... gawk remote: checking whether make sets $(MAKE)... yes remote: checking whether make supports nested variables... yes remote: checking whether make supports nested variables... (cached) yes remote: checking whether to enable maintainer-specific portions of Makefiles... no remote: checking for gcc... gcc remote: checking whether the C compiler works... yes remote: checking for C compiler default output file name... a.out remote: checking for suffix of executables... remote: checking whether we are cross compiling... no remote: checking for suffix of object files... o remote: checking whether we are using the GNU C compiler... yes remote: checking whether gcc accepts -g... yes remote: checking for gcc option to accept ISO C89... none needed remote: checking whether gcc understands -c and -o together... yes remote: checking for style of include used by make... GNU remote: checking dependency style of gcc... gcc3 remote: checking for gcc option to accept ISO C99... -std=gnu99 remote: checking for gcc option for ISO C99 w/o extensions... -std=c99 remote: checking how to run the C preprocessor... gcc -std=c99 -E remote: checking for grep that handles long lines and -e... /bin/grep remote: checking for egrep... /bin/grep -E remote: checking whether gcc -std=c99 needs -traditional... no remote: checking for ANSI C header files... yes remote: checking for sys/types.h... yes remote: checking for sys/stat.h... yes remote: checking for stdlib.h... yes remote: checking for string.h... yes remote: checking for memory.h... yes remote: checking for strings.h... yes remote: checking for inttypes.h... yes remote: checking for stdint.h... yes remote: checking for unistd.h... yes remote: checking minix/config.h usability... no remote: checking minix/config.h presence... no remote: checking for minix/config.h... no remote: checking whether it is safe to define __EXTENSIONS__... yes remote: checking for ar... ar remote: checking the archiver (ar) interface... ar remote: checking build system type... x86_64-pc-linux-gnu remote: checking host system type... x86_64-pc-linux-gnu remote: checking how to print strings... printf remote: checking for a sed that does not truncate output... /bin/sed remote: checking for fgrep... /bin/grep -F remote: checking for ld used by gcc -std=c99... /usr/bin/ld remote: checking if the linker (/usr/bin/ld) is GNU ld... yes remote: checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B remote: checking the name lister (/usr/bin/nm -B) interface... BSD nm remote: checking whether ln -s works... yes remote: checking the maximum length of command line arguments... 3458764513820540925 remote: checking whether the shell understands some XSI constructs... yes remote: checking whether the shell understands "+="... yes remote: checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu format... func_convert_file_noop remote: checking how to convert x86_64-pc-linux-gnu file names to toolchain format... func_convert_file_noop remote: checking for /usr/bin/ld option to reload object files... -r remote: checking for objdump... objdump remote: checking how to recognize dependent libraries... pass_all remote: checking for dlltool... no remote: checking how to associate runtime and link libraries... printf %s\n remote: checking for archiver @FILE support... @ remote: checking for strip... strip
