>With git >= 1.7.8 are submodules cloned into .git/modules and in
>submodule folder is only .git file.
I have no idea what happened or why only now everything is
exploding. That said, looks like possibly my tree has been
corrupted for a while. I have no idea what is the catalyst to start
the recent events.
Seems right now I have a mish-mash mixture of some modules with a
.git directory and some modules with a .git file pointing to a
respective .git directory in the root of the source tree.
Some modules have no .git directory in the module or in the root
.git directory. Like right now, tde-i18n is void of any .git
directory in either location. That is 1.1GB of files I don't want
to have to download when all I need is a respective .git directory
somewhere.
Running git pull does nothing to recreate the .git directory
somewhere.
Is there a fix for this?
Or, is there a way I can update my tree to move the .git folder
that exists in each module to ../../../.git/modules/ and create an
appropriate .git file in each module that points to
../../../.git/modules/{modulename}?
Darrell
>With git >= 1.7.8 are submodules cloned into .git/modules and in
>submodule folder is only .git file.
I'm using git-1.7.12.1, which is what I have been using since I
updated to Slackware 14.0 way back in February. I don't understand
why all of the sudden everything is exploding.
Darrell
>From a certain version of the GIT are ".git" folders of submodules
>placed into folder ".git/modules" in the "master" module.
Okay, I think I now see what you described. When did this change
occur? I have not updated my git package.
Why is this now happening only in the past several days?
Why am I now receiving all of these fatal messages? How do I stop
the messages?
The latest fatal is tde-i18n, the biggest pig module of them all.
Darrell
>There may be a better and quicker way, but in a case like this I
>would do a clean checkout. It takes a few hours, but at least you
>can be sure everything is as it should be.
How do I do that?
My fear is as my local tree continually self-explodes, I am going
to end up cloninge the entire tree, which at 4 or 5 GBs will take
all damn day.
There must be some kind of repair procedure?
Darrell
>From a certain version of the GIT are ".git" folders of submodules
>placed into folder ".git/modules" in the "master" module.
I no longer have any .git folders in any of the affected modules.
One by one they are disappearing. Every time I resync a new module
is affected. Something got corrupted and the proverbial hell is
breaking loose here. :-)
I hate git!
Darrell
All,
Within the past couple of days I now am getting a lot of these
types of messages when I attempt to sync my local tree:
fatal: destination path 'main/applications/ktorrent' already exists
and is not an empty directory.
Thus far the only fix I have found is to delete the entire module
and resync.
The problem is there is no .git directory in the affected modules.
I have no idea how to fix and searching the web is not helping.
There seems to be no end to the madness. With each resync a new
module is affected.
Please help!
Darrell
>I am noticing a peculiarity when I compile TQt3....
>
>Am I doing something wrong or are the -debug/-release configure
>options reversed?
Never mind. PEBKAC. I was using an environment variable $DEBUG
twice in two different places. The two different uses confused the
build script --- and confused me too. :-)
Darrell
Is there a such tool for DCOP like dbus-monitor for dbus?
I'm currently messing with bug 1768 and I wanna find out who (if anybody)
calls the logout method of ksmserver.
NOTE: I'm a total noob in DCOP as well as in tde initialization system.
All,
I am noticing a peculiarity when I compile TQt3. When I compile
with the -release option, my final package size is about 35MB
(txz). When I compile with the -debug option the final package size
is about 13.6 MB. I expected the opposite.
When I use -debug the build log is filled with -DQT_NO_DEBUG. When
I use -release I do not see -DQT_NO_DEBUG at all in the build log.
I expected the opposite.
I am presuming -debug means compiling with debugging symbols and -
release means do not compile debugging symbols.
Here are my build script configure options, where $DEBUG is either -
debug or -release:
echo "yes" | \
CFLAGS=$CPUOPT \
CXXFLAGS=$CPUOPT \
./configure \
-v \
-prefix $INSTALL_PREFIX \
-libdir $LIBDIR \
$DEBUG \
-I/usr/include/mysql \
-I/usr/include/freetype2/freetype \
-L/usr/lib${LIBDIRSUFFIX} \
-qt-imgfmt-png \
-qt-imgfmt-mng \
-qt-imgfmt-jpeg \
-qt-gif \
-qt-style-motif \
-system-zlib \
-system-libpng \
-system-libmng \
-system-libjpeg \
-shared \
-no-pch \
-thread \
-stl \
-no-exceptions \
-platform ${PLATFORM} \
-cups \
-ipv6 \
-nis \
-sm \
-largefile \
-xshape \
-xinerama \
-xcursor \
-xrandr \
-xrender \
-tablet \
-xkb \
-xft \
-plugin-imgfmt-mng \
-plugin-sql-mysql \
-plugin-sql-sqlite \
-plugin-style-cde \
-plugin-style-compact \
-plugin-style-motifplus \
-plugin-style-platinum \
-plugin-style-sgi \
-plugin-style-windows \
-lfontconfig \
-inputmethod \
-enable-opengl \
-dlopen-opengl \
$GLIBMAINLOOP \
|| exit 1
Am I doing something wrong or are the -debug/-release configure
options reversed?
Darrell