switch_all_submodules_to_head_and_clean -> Stopping at 'experimental'; script returned non-zero status.
Tim, all,
Is this OK? I have run into this error with the script after cloning the current repository:
01:02 archangel:/dat_e/tde> ./scripts/switch_all_submodules_to_head_and_clean Preparing /dat_e/tde for development use Enter your TDE GIT username []: drankin HEAD is now at 6df356b Reset submodule main/tdebase to latest HEAD Removing libqt-mt.so Removing libqt-mt.so.3 Removing libqt-mt.so.3.3 Already up-to-date. HEAD is now at 6df356b Reset submodule main/tdebase to latest HEAD Submodule 'experimental' () registered for path 'experimental' Submodule 'main/applications/abakus' () registered for path 'main/applications/abakus'
<snip>
Entering 'main/tdewebdev' Already up-to-date. Entering 'experimental' This script can only be run from a top level git directory. Exiting... Stopping at 'experimental'; script returned non-zero status.
I presume this is OK, but wanted to check before I start down a path with a messed up clone of the repository. What say the experts?
P.S. - How is the audiofile 3.2 -> 3.3 release and libpng 1.5.8 release impacting current building?
Tim, all,
Is this OK? I have run into this error with the script after cloning the current repository:
01:02 archangel:/dat_e/tde> ./scripts/switch_all_submodules_to_head_and_clean Preparing /dat_e/tde for development use Enter your TDE GIT username []: drankin HEAD is now at 6df356b Reset submodule main/tdebase to latest HEAD Removing libqt-mt.so Removing libqt-mt.so.3 Removing libqt-mt.so.3.3 Already up-to-date. HEAD is now at 6df356b Reset submodule main/tdebase to latest HEAD Submodule 'experimental' () registered for path 'experimental' Submodule 'main/applications/abakus' () registered for path 'main/applications/abakus'
<snip>
Entering 'main/tdewebdev' Already up-to-date. Entering 'experimental' This script can only be run from a top level git directory. Exiting... Stopping at 'experimental'; script returned non-zero status.
I presume this is OK, but wanted to check before I start down a path with a messed up clone of the repository. What say the experts?
This would mean that your top level directory does not have its .git/ folder for some reason. It should be safe to ignore, but if someone were to add another submodule to the TDE tree you would not receive it as an update from running that script (i.e. you would need to manually initialize the new submodule repository with "git clone").
P.S. - How is the audiofile 3.2 -> 3.3 release and libpng 1.5.8 release impacting current building?
If you receive build errors related to those releases please file a bug report. Otherwise there is no impact. ;-)
Tim
On 02/09/2012 01:42 AM, Timothy Pearson wrote: <snip>
This would mean that your top level directory does not have its .git/ folder for some reason. It should be safe to ignore, but if someone were to add another submodule to the TDE tree you would not receive it as an update from running that script (i.e. you would need to manually initialize the new submodule repository with "git clone").
Hmm,
I don't know how I would have gotten it without it. I used git clone 'http://drankin@scm.trinitydesktop.org/scm/git/tde' while in the /dat_e mount point. It shouldn't matter, but /dat_e is the mount point for a separate drive. i.e.:
# mount <snip> /dev/sde5 on /dat_e type ext3 (rw,relatime,errors=continue,data=ordered)
Here are the entries I ended up with:
07:33 archangel:/dat_e> ls -al total 40 drwxr-xr-x 9 david david 4096 Jan 19 22:28 dv drwx------ 2 root root 16384 Nov 14 2010 lost+found drwxr-xr-x 6 david david 4096 Feb 9 01:05 tde -rw-r--r-- 1 david david 4200 Jan 26 18:12 dv-bu-needed.txt
07:33 archangel:/dat_e> ls -al tde total 60 drwxr-xr-x 9 david david 4096 Feb 9 01:05 .git drwxr-xr-x 5 david david 4096 Feb 8 17:41 experimental drwxr-xr-x 27 david david 4096 Feb 8 17:37 main drwxr-xr-x 2 david david 4096 Feb 8 17:37 scripts -rw-r--r-- 1 david david 17653 Feb 9 01:05 .gitmodules -rw-r--r-- 1 david david 1558 Feb 8 17:37 README.GIT -rw-r--r-- 1 david david 11007 Feb 8 17:37 submodules
P.S. - How is the audiofile 3.2 -> 3.3 release and libpng 1.5.8 release impacting current building?
Good to hear. Both libpng 1.5.8 and audiofile 3.3 contain soname bumps libpng14 -> libpng15 and libaudiofile.so.0 -> libaudiofile.so.1. libpng breaks everything with an existing install (starting with kdm) and audiofile breaks sound events and basket notepads.
If you receive build errors related to those releases please file a bug report. Otherwise there is no impact. ;-)
Will do.
-
David C. Rankin -
Timothy Pearson