Send Pd-cvs mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.puredata.info/listinfo/pd-cvs
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Pd-cvs digest..."


Today's Topics:

   1. autobuild: pd-extended debian-stable-amd64 2012-09-18
      06.25.47 (pd auto builds)
   2. autobuild: pd-extended debian-testing-amd64 2012-09-18
      06.28.41 (pd buildbot)


----------------------------------------------------------------------

Message: 1
Date: Tue, 18 Sep 2012 06:55:06 -0400 (EDT)
From: [email protected] (pd auto builds)
Subject: [PD-cvs] autobuild: pd-extended debian-stable-amd64
        2012-09-18      06.25.47
To: [email protected]
Message-ID: <[email protected]>

last 20 errors ----------------------------------------
rsync error: syntax or usage error (code 1) at main.c(1236) [Receiver=3.0.7]
last 15 lines ----------------------------------------
                        
/home/pd/auto-build/pd-extended/packages/linux_make/build//usr/lib/pd-extended/extra/ekext
install: cannot stat `ninjacount-help.pd': No such file or directory
make[3]: *** [install-doc] Error 1
make[3]: Leaving directory `/home/pd/auto-build/pd-extended/externals/ekext'
make[2]: *** [ekext_install] Error 2
make[2]: Leaving directory `/home/pd/auto-build/pd-extended/externals'
make[1]: *** [externals_install] Error 2
make[1]: Leaving directory `/home/pd/auto-build/pd-extended/packages'
make: *** [install] Error 2
ls: cannot access 
/home/pd/auto-build/pd-extended/packages/linux_make/./Pd*.deb: No such file or 
directory
upload specs linux_make . deb
Uploading 
Unexpected local arg: debian
If arg is a remote file/dir, prefix it with a colon (:).
rsync error: syntax or usage error (code 1) at main.c(1236) [Receiver=3.0.7]

the full logfile - if it has been succesfully uploaded - can be viewed at:
http://autobuild.puredata.info/auto-build/2012-09-18/logs/2012-09-18_06.25.47_linux_debian-stable-amd64_pd-extended.txt



------------------------------

Message: 2
Date: Tue, 18 Sep 2012 07:02:05 -0400 (EDT)
From: [email protected] (pd buildbot)
Subject: [PD-cvs] autobuild: pd-extended debian-testing-amd64
        2012-09-18      06.28.41
To: [email protected]
Message-ID: <[email protected]>

last 20 errors ----------------------------------------
recordV4L2.cpp:81:5: error: '::close' has not been declared
recordV4L2.cpp:159:3: error: '::write' has not been declared
recordV4L2.cpp:184:3: error: '::write' has not been declared
rsync error: syntax or usage error (code 1) at main.c(1246) [Receiver=3.0.9]
last 15 lines ----------------------------------------
make[4]: *** [all-recursive] Error 1
make[4]: Leaving directory 
`/home/pd/auto-build/pd-extended/externals/Gem/plugins'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory `/home/pd/auto-build/pd-extended/externals/Gem'
make[2]: *** [/home/pd/auto-build/pd-extended/externals/Gem/Gem.pd_linux] Error 
2
make[2]: Leaving directory `/home/pd/auto-build/pd-extended/externals'
make[1]: *** [externals_install] Error 2
make[1]: Leaving directory `/home/pd/auto-build/pd-extended/packages'
make: *** [install] Error 2
ls: cannot access 
/home/pd/auto-build/pd-extended/packages/linux_make/./Pd*.deb: No such file or 
directory
upload specs linux_make . deb
Uploading 
Unexpected local arg: README
If arg is a remote file/dir, prefix it with a colon (:).
rsync error: syntax or usage error (code 1) at main.c(1246) [Receiver=3.0.9]

the full logfile - if it has been succesfully uploaded - can be viewed at:
http://autobuild.puredata.info/auto-build/2012-09-18/logs/2012-09-18_06.28.41_linux_debian-testing-amd64_pd-extended.txt



------------------------------

_______________________________________________
Pd-cvs mailing list
[email protected]
http://lists.puredata.info/listinfo/pd-cvs


End of Pd-cvs Digest, Vol 91, Issue 19
**************************************

Reply via email to